| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-testers(at)postgresql(dot)org |
| Subject: | Re: Conditional trigger missing from pg_dump |
| Date: | 2010-03-25 17:45:24 |
| Message-ID: | 21052.1269539124@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-testers |
Josh Berkus <josh(at)agliodbs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-03-25 18:13:40 | Re: Conditional trigger missing from pg_dump |
| Previous Message | Josh Berkus | 2010-03-25 17:41:34 | Conditional trigger missing from pg_dump |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-03-25 18:13:40 | Re: Conditional trigger missing from pg_dump |
| Previous Message | Josh Berkus | 2010-03-25 17:41:34 | Conditional trigger missing from pg_dump |