Re: pg_dump -j against standbys

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump -j against standbys
Date: 2016-05-26 09:12:06
Message-ID: CABUevExRKMUKrJg=CdU6xaAfppZwE3kJjfm+R8XS4LsMD9GkSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 25, 2016 at 4:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> >> Also, why didn't you keep using ExecuteSqlQueryForSingleRow()?
>
> > The reason I did that is that ExecuteSqlQueryForSingleRow() is a static
> > method in pg_dump.c. I was planning to go back and review that, and
> > consider moving it, but I forgot it :S
>
> > I think the clean thing is probably to use that one, and also move it
> over
> > to not be a static method in pg_dump.c, but instead sit next to
> > ExecuteSqlQuery in pg_backup_db.c. Do you agree that's reasonable, and
> > something that's OK to backpatch?
>
> No objection here, since it wouldn't be exposed outside pg_dump in any
> case.
>

Here's an updated patch based on this,and the other feedback.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

Attachment Content-Type Size
pg_dump_sync_snapshots_2.patch text/x-patch 5.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2016-05-26 09:55:51 Fix a failure of pg_dump with !HAVE_LIBZ
Previous Message Dean Rasheed 2016-05-26 07:26:41 Re: RLS related docs