Re: Refactor pg_dump as a library?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Jakob Egger <jakob(at)eggerapps(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Refactor pg_dump as a library?
Date: 2016-04-14 17:01:44
Message-ID: 20160414170144.22lunah62qnf53sy@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016-04-14 13:16:20 +0200, Andreas Karlsson wrote:
> I am personally not a fan of the pg_get_Xdef() functions due to their heavy
> reliance on the syscache which feels rather unsafe in combination with
> concurrent DDL.

I'm not sure I find that convincing: The state portrayed by the syscache
is th state COPY/SELECT et al will be using. I think the angle to
attack this is rather to allow blocking 'globally visible' DDL
efficiently and correctly, rather than the hack pg_dump is using right now.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2016-04-14 17:04:00 Re: Pglogical questions and problems
Previous Message Joshua D. Drake 2016-04-14 16:59:49 Re: Pglogical questions and problems