| From: | Miroslav Šimulčík <simulcik(dot)miro(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: function for setting/getting same timestamp during whole transaction |
| Date: | 2013-02-09 09:13:23 |
| Message-ID: | CAHRNM68ifYbX8Ef4L9ueMwOEdFgekKTjO4-QEqdVV00jia6YoA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> I might be confused here, but I think the point is that if you pass
> "true" as the third argument to set_config, the setting lasts only for
> the duration of the current transaction, like SET LOCAL. Which I
> think solves your problem.
Yes, but at the end of transaction it is reset to the value it has before
transaction (session level value), which can be nonempty. I wrote example
about this problem lately in this thread.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carlo Stonebanks | 2013-02-09 17:52:31 | Tcl & PG on Win 7 64 bit - is it working for anyone? |
| Previous Message | Chris Travers | 2013-02-09 05:02:25 | Use case for deferrable check constraints, given inherited tables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2013-02-09 09:25:14 | Re: Considering Gerrit for CFs |
| Previous Message | Pavel Stehule | 2013-02-09 08:52:00 | performance regression in 9.2 CTE with SRF function |