See
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=805093113df3f09979cb0e55e857976aad77b8af
Please send any corrections by Sunday.
regards, tom lane
On 11/7/20 11:21 PM, Tom Lane wrote:
> Tomas Vondra writes:
>> On 11/7/20 3:52 AM, Tom Lane wrote:
>>> Do you have some suggested text?
>
>> I think this might work:
>
> I dunno ... given that we have zero field reports, I doubt this is
> something we need to tell every BRIN user to do. The tex
Tomas Vondra writes:
> On 11/7/20 3:52 AM, Tom Lane wrote:
>> Do you have some suggested text?
> I think this might work:
I dunno ... given that we have zero field reports, I doubt this is
something we need to tell every BRIN user to do. The text I put in
earlier today just recommends reindexin
Hi,
On 11/7/20 3:52 AM, Tom Lane wrote:
> Tomas Vondra writes:
>> We should probably include instructions what to do about the BRIN
>> data corruption fixed by 7577dd8480 - a query to list might be
>> affected by the bug and should be rebuilt.
>
> Do you have some suggested text?
>
I think thi
Tomas Vondra writes:
> We should probably include instructions what to do about the BRIN
> data corruption fixed by 7577dd8480 - a query to list might be
> affected by the bug and should be rebuilt.
Do you have some suggested text?
regards, tom lane
On Fri, 06 Nov 2020 17:07:12 -0500
Tom Lane wrote:
> See
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c66a3225e07b5098a796f24588a6b81bfdedd2fd
>
> Please send any corrections by Sunday.
>
We should probably include instructions what to do about the BRIN
data corrupti
See
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c66a3225e07b5098a796f24588a6b81bfdedd2fd
Please send any corrections by Sunday.
regards, tom lane
On 5/5/19 12:24 AM, Thomas Munro wrote:
> On Sun, May 5, 2019 at 2:35 PM Jonathan S. Katz wrote:
>> On 5/3/19 6:29 PM, Tom Lane wrote:
>>> See
>>>
>>> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8b3bce2017b15e05f000c3c5947653a3e2c5a29f
>>>
>>> Please send any corrections by
On Sun, May 5, 2019 at 2:35 PM Jonathan S. Katz wrote:
> On 5/3/19 6:29 PM, Tom Lane wrote:
> > See
> >
> > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8b3bce2017b15e05f000c3c5947653a3e2c5a29f
> >
> > Please send any corrections by Sunday.
>
> Attached is a draft of the pres
On 5/3/19 6:29 PM, Tom Lane wrote:
> See
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8b3bce2017b15e05f000c3c5947653a3e2c5a29f
>
> Please send any corrections by Sunday.
Attached is a draft of the press release to go out. Please let me know
if there are any inaccuracies
Thomas Munro writes:
> On Sat, May 4, 2019 at 1:29 PM Tom Lane wrote:
>> Yeah, I didn't really think it was worth distinguishing. If there
>> is some more general term that covers both calls, maybe we should
>> use that?
> I would just do s/fsync/fsync and sync_file_range/. And I guess also
>
Andrew Gierth writes:
> "Michael" == Michael Paquier writes:
> Michael> I have noticed a typo:
> Michael>Errors, such as lack of permissions to read the directory,
> were not
> Michael>detected or reported correctly; instead the code silently
> acted as
> Michael> - tho
> "Michael" == Michael Paquier writes:
Michael> I have noticed a typo:
Michael>Errors, such as lack of permissions to read the directory,
were not
Michael>detected or reported correctly; instead the code silently
acted as
Michael> - though the directory were empty.
On Fri, May 03, 2019 at 06:29:35PM -0400, Tom Lane wrote:
> Please send any corrections by Sunday.
I have noticed a typo:
--- a/doc/src/sgml/release-11.sgml
+++ b/doc/src/sgml/release-11.sgml
@@ -982,7 +982,7 @@ Branch: REL9_4_STABLE [81f5b3283] 2019-03-04
09:50:24 +0900
Errors, such
On Sat, May 4, 2019 at 1:29 PM Tom Lane wrote:
> Thomas Munro writes:
> > On Sat, May 4, 2019 at 10:29 AM Tom Lane wrote:
> > + Tolerate EINVAL and ENOSYS
> > + error results, where appropriate, for fsync calls (Thomas Munro,
> > + James Sewell)
>
> > Nit-picking: ENOSYS is for sy
Thomas Munro writes:
> On Sat, May 4, 2019 at 10:29 AM Tom Lane wrote:
> + Tolerate EINVAL and ENOSYS
> + error results, where appropriate, for fsync calls (Thomas Munro,
> + James Sewell)
> Nit-picking: ENOSYS is for sync_file_range, EINVAL is for fsync.
Yeah, I didn't really th
On Sat, May 4, 2019 at 10:29 AM Tom Lane wrote:
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8b3bce2017b15e05f000c3c5947653a3e2c5a29f
>
> Please send any corrections by Sunday.
+ Tolerate EINVAL and ENOSYS
+ error results, where appropriate, for fsync calls (Thom
See
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8b3bce2017b15e05f000c3c5947653a3e2c5a29f
Please send any corrections by Sunday.
regards, tom lane
18 matches
Mail list logo
