Re: ALTER TABLE ... NOREWRITE option

From: Noah Misch <noah(at)leadboat(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER TABLE ... NOREWRITE option
Date: 2012-12-04 03:34:12
Message-ID: 20121204033412.GA29742@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 03, 2012 at 11:37:17AM +0100, Dimitri Fontaine wrote:
> Noah Misch <noah(at)leadboat(dot)com> writes:
> > Acquiring the lock could still take an unpredictable amount of time.
>
> I think there's a new GUC brewing about setting the lock timeout
> separately from the statement timeout, right?

Yes.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2012-12-04 03:37:21 Reducing pg_dumpall errors
Previous Message Amit Kapila 2012-12-04 03:22:44 Re: Proposal for Allow postgresql.conf values to be changed via SQL