Re: BUG #13660: serializable snapshotting hangs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: Chris Pacejo <cpacejo(at)clearskydata(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13660: serializable snapshotting hangs
Date: 2015-10-07 13:37:09
Message-ID: 22977.1444225029@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> Incorrect. Like vacuum and other visibility-related operations,
> long-running transactions in other databases in the same "cluster"
> (in the sense of a group of backends running under a single
> postmaster) will be an issue. I seem to recall that it was
> non-trivial to limit things in general to a single database, but
> perhaps the DEFERRABLE feature could be enhanced to do that without
> too much pain.

How will that work in the case of serialized access to a shared catalog?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2015-10-07 13:54:30 Re: BUG #13660: serializable snapshotting hangs
Previous Message Kevin Grittner 2015-10-07 12:41:17 Re: BUG #13660: serializable snapshotting hangs