Prev: [HACKERS] Ask help for putting SP-Gist into postgresql
Next: question (or feature-request): over ( partition by ...order by LIMIT N)
From: Tom Lane on 25 Mar 2010 13:45
Josh Berkus <josh(a)agliodbs.com> writes:
> It looks like pg_dump was never modified to include conditional
> triggers. If you look in pg_dump.c, there's no provision to dump the
> FOR UPDATE OF part of the trigger declaration.

That proves nothing; it could be relying on server-side code to produce
the declaration.

> This was discovered by Dave Olszewski while testing conditional triggers.

Please show a specific example of what you're worried about.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Josh Berkus on 25 Mar 2010 14:13

>> This was discovered by Dave Olszewski while testing conditional triggers.
>
> Please show a specific example of what you're worried about.

I'll get you a reproduceable test case later today. In our testing, the
conditional part of the trigger was not being dumped.

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [HACKERS] Ask help for putting SP-Gist into postgresql
Next: question (or feature-request): over ( partition by ...order by LIMIT N)