Re: pg_dump with both --serializable-deferrable and -j

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump with both --serializable-deferrable and -j
Date: 2015-01-28 21:33:23
Message-ID: 382502844.1254487.1422480803596.JavaMail.yahoo@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:

> Having pg_dump use repeatable read transactions for the processes
> that import the snapshot would work fine, as long as they are
> reading a snapshot which was captured by a serializable read only
> deferrable transaction.

It looks like the attached patch does it (although it is only
lightly tested so far and only on the master branch). This seems
like a back-patchable bug fix (to 9.3).

Thoughts?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment Content-Type Size
pg_dump-jobs-and-serializable-v1.patch text/x-diff 561 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-01-28 21:34:28 Re: Make hba available to client code
Previous Message Andrew Dunstan 2015-01-28 21:32:51 Re: Make hba available to client code