| From: | Durumdara <durumdara(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Really unique session ID - PID + connection timestamp? |
| Date: | 2016-04-09 08:30:49 |
| Message-ID: | CAEcMXhkyUMmT3wiKnyWwSK1Xv3gFot46AoTM+6JxWhya3dGWjg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dear Everybody!
In MS we had a "persistent lock" structure and method.
This over transactions because based on real records in a real table with
pri key (tablename + id).
For garbaging we had a special session info.
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?
Thanks for your help!
dd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2016-04-09 10:07:08 | Re: Really unique session ID - PID + connection timestamp? |
| Previous Message | David G. Johnston | 2016-04-09 07:29:34 | Re: 9.5 - Is there any way to disable automatic rollback? |