doc: remove XML comments around compute_query_id PG14 rel text
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/f39b21e6a25c7269f50a709aa874e321e6f84b20
Modified Files
--
doc/src/sgml/release-14.sgml | 2 --
1 file changed, 2 deletions(-)
doc: update PG 14 release notes for compute_query_id change
Also remove ALTER TYPE ...SUBSCRIPT, and update for all current commits.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/6cb5346cb15d56e6ba8288b891c7098f0aecdadc
Modified Files
--
doc/src/sgml/
On 2021-May-15, Tom Lane wrote:
> I wrote:
> > Alvaro Herrera writes:
> >> Allow compute_query_id to be set to 'auto' and make it default
>
> > culicidae seems unhappy: ...
> > Not sure why it's only that animal.
>
> Oh ... EXEC_BACKEND, likely, seeing that the Windows animals
> are going red a
Unbreak EXEC_BACKEND build
Per buildfarm
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/354f32d01dedc2c86a05be298a62cdae9710d203
Modified Files
--
src/backend/postmaster/postmaster.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
I wrote:
> Alvaro Herrera writes:
>> Allow compute_query_id to be set to 'auto' and make it default
> culicidae seems unhappy: ...
> Not sure why it's only that animal.
Oh ... EXEC_BACKEND, likely, seeing that the Windows animals
are going red as well.
regards, tom lane
Alvaro Herrera writes:
> Allow compute_query_id to be set to 'auto' and make it default
culicidae seems unhappy:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2021-05-15%2018%3A20%3A08
/mnt/resource/andres/bf/culicidae/HEAD/pgsql.build/../pgsql/src/backend/postmaster/post
Allow compute_query_id to be set to 'auto' and make it default
Allowing only on/off meant that all either all existing configuration
guides would become obsolete if we disabled it by default, or that we
would have to accept a performance loss in the default config if we
enabled it by default. By
Be more careful about barriers when releasing BackgroundWorkerSlots.
ForgetBackgroundWorker lacked any memory barrier at all, while
BackgroundWorkerStateChange had one but unaccountably did
additional manipulation of the slot after the barrier. AFAICS,
the rule must be that the barrier is immedia
Be more careful about barriers when releasing BackgroundWorkerSlots.
ForgetBackgroundWorker lacked any memory barrier at all, while
BackgroundWorkerStateChange had one but unaccountably did
additional manipulation of the slot after the barrier. AFAICS,
the rule must be that the barrier is immedia
Be more careful about barriers when releasing BackgroundWorkerSlots.
ForgetBackgroundWorker lacked any memory barrier at all, while
BackgroundWorkerStateChange had one but unaccountably did
additional manipulation of the slot after the barrier. AFAICS,
the rule must be that the barrier is immedia
Be more careful about barriers when releasing BackgroundWorkerSlots.
ForgetBackgroundWorker lacked any memory barrier at all, while
BackgroundWorkerStateChange had one but unaccountably did
additional manipulation of the slot after the barrier. AFAICS,
the rule must be that the barrier is immedia
Be more careful about barriers when releasing BackgroundWorkerSlots.
ForgetBackgroundWorker lacked any memory barrier at all, while
BackgroundWorkerStateChange had one but unaccountably did
additional manipulation of the slot after the barrier. AFAICS,
the rule must be that the barrier is immedia
Be more careful about barriers when releasing BackgroundWorkerSlots.
ForgetBackgroundWorker lacked any memory barrier at all, while
BackgroundWorkerStateChange had one but unaccountably did
additional manipulation of the slot after the barrier. AFAICS,
the rule must be that the barrier is immedia
13 matches
Mail list logo
