Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Should buffer of initialization fork have aBM_PERMANENT flag - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Should buffer of initialization fork have aBM_PERMANENT flag
Date
Msg-id CAB7nPqSQCwbCsnB_W7uW85h3hytnX2TinwB=BZ8_RnB+CYMsbw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Should buffer of initialization fork have aBM_PERMANENT flag  (Artur Zakirov <a.zakirov@postgrespro.ru>)
Responses Re: [HACKERS] Should buffer of initialization fork have aBM_PERMANENT flag  (Artur Zakirov <a.zakirov@postgrespro.ru>)
List pgsql-hackers
Tree view 
On Thu, Mar 9, 2017 at 10:25 PM, Artur Zakirov <a.zakirov@postgrespro.ru> wrote:
> I think this is good fixes. I've checked them. And in my opinion they are
> correct.
>
> The code also is good.

Having something with conflicts is not nice, so attached is a rebased version.

> I have run regression and TAP tests. They all passed without error.
>
> I think the patch can be marked as "Ready for Committer" after rebase.

Thanks for the review.
-- 
Michael

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] contrib modules and relkind check
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] pgsql: Throw an error if a DATA() line contains wrong # of attributes.