leftover file. However, the background process crash could leave the file
> for a long time, since the crash may not lead to postmaster restart. Also,
> we will get inclined to add sessionid column in pg_stat_activity (the concept
> of session ID can be useful for other uses.)
Sounds
Thanks for a cool feature with nice UI. Can I expect it to work for background
processes? For troubleshooting, I wanted to investigate how autovacuum
launcher/worker behaves by having them emit DEBUG messages.
(My comments follow)
From: Kyotaro HORIGUCHI [mailto:horiguchi.kyot...@lab.ntt.co.
> > > I.e. it seems entirely possible that backends stop/start between
> > > > > > determining the PID, and the ALTER SESSION creating the file, and it
> > > > > > actually being processed. By the time that happens an entirely
> > > > > >
) wrote:
> > > > > Leaving the desirability of the feature aside, isn't this racy as
> > > > > hell?
> > > > > I.e. it seems entirely possible that backends stop/start between
> > > > > determining the PID, and the ALTER SESSION cre
ature aside, isn't this racy as hell?
> > > > I.e. it seems entirely possible that backends stop/start between
> > > > determining the PID, and the ALTER SESSION creating the file, and it
> > > > actually being processed. By the time that happens an entirely di
ossible that backends stop/start between
> > > determining the PID, and the ALTER SESSION creating the file, and it
> > > actually being processed. By the time that happens an entirely different
> > > session might be using that pid.
> >
> > That seems like s
On 2019-01-29 20:52:08 -0500, Stephen Frost wrote:
> * Andres Freund (and...@anarazel.de) wrote:
> > Leaving the desirability of the feature aside, isn't this racy as hell?
> > I.e. it seems entirely possible that backends stop/start between
> > determining the PID, and
removed at
> > > startup or at the end of the coressponding session.
> > >
> > >- Add a new syntax like this:
> > > ALTER SESSION WITH (pid=)
> > > SET configuration_parameter {TO | =} {value | 'value' | DEFAULT}
> > >
d new configuration file "postgresql.conf." and
> > pg_reload_conf() let the session with the PID loads it as if
> > it is the last included file. All such files are removed at
> > startup or at the end of the coressponding session.
> >
> >- A
t; startup or at the end of the coressponding session.
> >
> >- Add a new syntax like this:
> > ALTER SESSION WITH (pid=)
> > SET configuration_parameter {TO | =} {value | 'value' | DEFAULT}
> > RESET configuration_parame
th the PID loads it as if
> it is the last included file. All such files are removed at
> startup or at the end of the coressponding session.
>
>- Add a new syntax like this:
> ALTER SESSION WITH (pid=)
> SET configuration_parameter {TO | =} {value
11 matches
Mail list logo
