| From: | bricklen <bricklen(at)gmail(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump --snapshot |
| Date: | 2013-05-07 17:23:51 |
| Message-ID: | CAGrpgQ9AgTmFCGGrjM4aKFEq8W4ZCLe_SaQAhxKVdSt_e5aXdw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 7, 2013 at 10:02 AM, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>wrote:
> Rather than take some locks, you can now prevent the database objects
> from changing with an event trigger. pg_dump could install that event
> trigger in a preparing transaction, then do its work as currently, then
> when done either remove or disable the event trigger.
>
> All the event trigger has to do is unconditionnaly raise an exception
> with a message explaining that no DDL command is accepted during when a
> dump is in progress.
>
I'm thinking of a case where a hot standby is executing a pg_dump and DDL
is issued on the master -- would that cause any unexpected problems on the
hot standby?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2013-05-07 17:28:18 | Re: corrupt pages detected by enabling checksums |
| Previous Message | Robert Haas | 2013-05-07 17:20:48 | Re: corrupt pages detected by enabling checksums |