From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-testers@postgresql.org
Subject: Re: Conditional trigger missing from pg_dump
Date: Thu, 25 Mar 2010 13:45:24 -0400
Message-ID: <21052.1269539124@sss.pgh.pa.us> (raw)
In-Reply-To: <4BABA04E.6010603@agliodbs.com>
References: <4BABA04E.6010603@agliodbs.com>
Josh Berkus <josh@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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-testers@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, pgsql-hackers@postgresql.org
Subject: Re: Conditional trigger missing from pg_dump
In-Reply-To: <21052.1269539124@sss.pgh.pa.us>
References: <4BABA04E.6010603@agliodbs.com> <21052.1269539124@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox