On Sun, Jul 23, 2017 at 5:48 PM, Tom Lane wrote:
> Greg Atkins writes:
>> would you like a bug report to track this?
>
> No, it's already dealt with. In any case, your original email was good
> enough --- we track bugs these days more by message-ID than anything else.
This has been fixed by the
Greg Atkins writes:
> would you like a bug report to track this?
No, it's already dealt with. In any case, your original email was good
enough --- we track bugs these days more by message-ID than anything else.
regards, tom lane
--
Sent via pgsql-general mailing list
Tom,
would you like a bug report to track this?
On Sat, Jul 22, 2017 at 07:00:03PM -0400, Tom Lane wrote:
> Greg Atkins writes:
> > I have a DB with an event trigger, which I am dumping with
> > pg_dump -Fc --no-acl --no-owner [db_name] > [dump_file]
>
> > In my dump file, I can't find any DROP
Greg Atkins writes:
> I have a DB with an event trigger, which I am dumping with
> pg_dump -Fc --no-acl --no-owner [db_name] > [dump_file]
> In my dump file, I can't find any DROP EVENT TRIGGER statement.
Well, you wouldn't, for lack of -c ... but yes, it seems you don't
get a DROP EVENT TRIGGER
I have a DB with an event trigger, which I am dumping with
pg_dump -Fc --no-acl --no-owner [db_name] > [dump_file]
In my dump file, I can't find any DROP EVENT TRIGGER statement.
In src/bin/pg_dump/pg_dump.c, dumpEventTrigger() calls ArchiveEntry() with a ""
argument for the dropStmt parameter.