| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Date: | 2016-04-13 19:10:33 |
| Message-ID: | 570E99A9.7090605@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 4/12/16 12:30 PM, Tom Lane wrote:
> It'd be good if you document the problems you found somewhere, before
> you forget them, just in case somebody does want to try to lift the
> restriction. I agree that scattered code comments wouldn't be the way.
> Just a quick email to -hackers to get the info into the archives
> might be enough.
I think a code comment pointing at the archived message would be good
though...
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-04-13 19:21:05 | Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Previous Message | Kevin Grittner | 2016-04-13 19:08:49 | Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2016-04-13 19:17:08 | Re: [patch] \crosstabview documentation |
| Previous Message | Jim Nasby | 2016-04-13 19:08:58 | Re: sign function with INTERVAL? |