[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-bugs
Subject:    RE: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor
From:       "Boyer, Maxime (he/him | il/lui)" <Maxime.Boyer () cra-arc ! gc ! ca>
Date:       2023-10-24 19:12:30
Message-ID: 9a0da706031f412c8119258f58ce3bf6 () cra-arc ! gc ! ca
[Download RAW message or body]

Categorization: 
Unclassified 

Thank you all! :) I changed the setting back to 0 and we're not getting the error \
anymore. I have another error from pg11 I'll submit a new bug for.

Maxime

-----Original Message-----
From: Thomas Munro <thomas.munro@gmail.com> 
Sent: October 21, 2023 5:29 PM
To: Boyer, Maxime (he/him | il/lui) <Maxime.Boyer@cra-arc.gc.ca>
Cc: Alexander Lakhin <exclusion@gmail.com>; Tom Lane <tgl@sss.pgh.pa.us>; Andres \
                Freund <andres@anarazel.de>; pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18165: Could not duplicate handle for \
"Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor

On Sun, Oct 22, 2023 at 4:38 AM Boyer, Maxime (he/him | il/lui) \
<Maxime.Boyer@cra-arc.gc.ca> wrote:
> You guys are good! I did set min_dynamic_shared_memory to 2 GB in the new config, \
> which didn't exist on 11. I can set it to 0 and give it a try on Tuesday. Does 2 GB \
> seem overkill? We have plenty of memory to go by.

Apparently it has never worked on Windows and you're the first to notice and report \
that, so we can't expect anyone to have platform-specific experience with that.  But \
on other OSes we've seen it improve performance of large parallel joins and parallel \
vacuum, especially when 'huge pages' are configured.  (Note that we had reports that \
our huge page support for windows stopped working on recent Windows versions, \
addressed in PostgreSQL 16 by commit fdd8937c, so YMMV on PostgreSQL 14.)

Thanks for the report, and to Alexander for testing.  I've pushed the fix now, so it \
will ship in the next point release in a few weeks.  In the meantime, the workaround \
is to set it to 0.


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic