| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | drkp(at)csail(dot)mit(dot)edu, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: serializable read only deferrable |
| Date: | 2010-12-06 18:15:47 |
| Message-ID: | 29028.1291659347@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> I reviewed the documentation and played around with this a bit and
> can't find any areas where the current PostgreSQL implementation of
> READ ONLY is incompatible with what is needed for the SSI
> optimizations where it is used. There are a large number of tests
> which exercise this, and they're all passing.
> Did you have something in particular in mind which I should check?
I did not, just thought it was a point that merited examination.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-12-06 18:23:36 | Re: allow COPY routines to read arbitrary numbers of fields |
| Previous Message | Kevin Grittner | 2010-12-06 18:11:18 | Re: WIP patch for parallel pg_dump |