Re: Really unique session ID - PID + connection timestamp? - Mailing list pgsql-general

From Stephen Frost
Subject Re: Really unique session ID - PID + connection timestamp?
Date
Msg-id 20160409115712.GT10850@tamriel.snowman.net
Whole thread Raw
In response to Re: Really unique session ID - PID + connection timestamp?  (Christoph Berg <cb@df7cb.de>)
Responses Re: Really unique session ID - PID + connection timestamp?
List pgsql-general
* Christoph Berg (cb@df7cb.de) wrote:
> Re: Durumdara 2016-04-09 <CAEcMXhkyUMmT3wiKnyWwSK1Xv3gFot46AoTM+6JxWhya3dGWjg@mail.gmail.com>
> > In MS the session id is smallint, so it can repeats after server restarts,
> > but my coll. found a "session creation timestamp".
> > This is a key which unique.
> > With this we can check for died sessions and we can clean their records.
> >
> > We want create same mechanism.
> > I know there are adv. locks in PG, but I want to use session id.
> >
> > This could be:
> > pg_backend_pid()
> >
> > May pid repeats.
> > Where I can get timestamp or some other unique data with I can create a
> > combined primary key?
>
> Btw, what you are describing is exactly what %c in log_line_prefix
> does.

That's not currently exposed at an SQL level anywhere though, is it?
Perhaps we should add a way to get that.  Another thought would be to
essentially expose 'log_line_prefix()' at the SQL level but I'm not sure
that generally makes sense.  We could also have an explicit function to
get MyStartTime, similar to pg_backend_pid().

Thanks!

Stephen

Attachment

pgsql-general by date:

Previous
From: Durumdara
Date:
Subject: Re: Really unique session ID - PID + connection timestamp?
Next
From: Christoph Berg
Date:
Subject: Re: Really unique session ID - PID + connection timestamp?