From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
Date: | 2018-09-18 21:38:07 |
Message-ID: | 20180918213807.GA1650@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Tue, Sep 18, 2018 at 10:45:09AM -0400, Tom Lane wrote:
> In the meantime, we might be well advised to revert this patch in
> v11 and just continue to work on the problem in HEAD. I see now
> that this wasn't something to cram in during late beta ...
I can see that you have reverted the change just before I was able to
reply. Thanks I was going to do the same. Also, if we cannot find a
clear solution for HEAD rather soon, say by tomorrow, let's also remove
it there as well and go ack to the blackboard. I still want to test a
couple of other solutions first.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2018-09-18 22:56:58 | pgsql: Add support for nearest-neighbor (KNN) searches to SP-GiST |
Previous Message | Tom Lane | 2018-09-18 21:34:23 | pgsql: Revert "Allow concurrent-safe open() and fopen() in frontend cod |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-09-18 21:54:51 | Re: Collation versioning |
Previous Message | Thomas Munro | 2018-09-18 20:34:36 | Re: Collation versioning |