Skip to content

Cannot parse string: COMMENT ON COLUMN #260

@garykuipers

Description

@garykuipers

Apparently, form a comment in August 2018:

Postgres changed the way that search path semantics are used in pg_dump in response to this:
https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path

The affect took place earlier this year (March 2018) and affects all supported versions of postgres/pg_dump.

This affects all users of apgdiff, so it would be good to see a fix to address it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions