Re: restrict global access to be readonly

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, happy times <guangzhouzhang(at)qq(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, "funnyxj(dot)fxj" <funnyxj(dot)fxj(at)alibaba-inc(dot)com>, "dingqi(dot)lxb" <dingqi(dot)lxb(at)taobao(dot)com>
Subject: Re: restrict global access to be readonly
Date: 2015-02-15 16:24:48
Message-ID: 20150215162448.GD15326@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-02-14 17:28:38 -0600, Jim Nasby wrote:
> Throw an error in AssignTransactionId/GetNewTransactionId? I see 4 calls to
> Get*TransactionId in logical replication, though arguably if we're fixing
> that we should look at doing something special for Slony and the
> likes.

I don't think there are any xid assignments in the logical decoding
code. There's a couple error checks erroring out if an xid has been
assigned, but those use GetTopTransactionIdIfAny(), i.e. don't assign an
id.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2015-02-15 16:36:13 Re: New CF app deployment
Previous Message Florian Pflug 2015-02-15 16:14:21 Re: restrict global access to be readonly