Re: [PATCH] New [relation] option engine

From: Nikolay Shaplov <dhyan(at)nataraj(dot)su>
To: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Langote <amitlangote09(at)gmail(dot)com>, Nikolay Shaplov <dhyan(at)nataraj(dot)su>
Subject: Re: [PATCH] New [relation] option engine
Date: 2022-05-04 15:15:51
Message-ID: 28479319.bbFReQmD5n@thinkpad-pgpro
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

В письме от суббота, 16 апреля 2022 г. 17:15:34 MSK пользователь Nikolay
Shaplov написал:

Changed NoLock to AccessShareLock. This will remove last FIXME from the patch.

As more experienced pg-developers told me, you can call relation_open with
AccessShareLock, on a table you are going to work with, any time you like,
without being ashamed about it.

But this lock is visible when you have prepared transaction, so have to update
twophase test of test_decoding extension.

Nikolay Shaplov aka Nataraj
Fuzzing Engineer at Postgres Professional
Matrix IM:

Attachment Content-Type Size
new_options_take_two_v02.diff text/x-patch 192.0 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-05-04 15:16:12 Re: configure openldap crash warning
Previous Message Erik Rijkers 2022-05-04 14:39:45 Re: SQL/JSON: FOR ORDINALITY bug