| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | 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: Reducing Catalog Locking |
| Date: | 2014-10-31 13:59:27 |
| Message-ID: | CA+TgmoZ13xZ2FwCybyBo5mDsAEVOX5trQMvM986hZScmJJiyDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 31, 2014 at 9:54 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> But more to the point, this seems like optimizing pg_dump startup by
>> adding overhead everywhere else, which doesn't really sound like a
>> great tradeoff to me.
>
> Well, it'd finally make pg_dump "correct" under concurrent DDL. That's
> quite a worthwile thing.
Yeah, exactly. I agree with Tom that the overhead might be a concern.
But on the other hand, nobody has been more concerned about the
failure of pg_dump to handle this issue correctly than Tom.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2014-10-31 14:00:52 | Re: tracking commit timestamps |
| Previous Message | Andres Freund | 2014-10-31 13:54:21 | Re: Reducing Catalog Locking |