Re: documentation about explicit locking

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: documentation about explicit locking
Date: 2018-07-30 20:25:50
Message-ID: ec2777ac-4fd8-afe5-3757-d0be5a9dbcfd@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20/07/2018 02:30, Amit Langote wrote:
> We don't explicitly mention what locks we take on system catalogs
> elsewhere, but CREATE COLLATION is different from other commands, so I'm
> fine with adding more details as you suggest, so updated the text.

committed the documentation change

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-07-30 20:27:14 Re: documentation about explicit locking
Previous Message 'Andres Freund' 2018-07-30 20:17:04 Re: Recovery performance of standby for multiple concurrent truncates on large tables