| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Autoanalyze and OldestXmin |
| Date: | 2011-06-08 22:39:08 |
| Message-ID: | 016FA578-A1C8-4232-A5BF-017C67A77EB3@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jun 8, 2011, at 10:33 AM, Greg Stark wrote:
> This is kind of like the other property it would be nice to know about transactions: that they've locked all the tables they're going to lock.
That sounds like something I've wanted for a very long time: the ability for a transaction to say exactly what tables it's going to access. Presumably disallowing it from taking out any more table locks (anything you do on a table needs at least a share lock, right?) would take care of that.
If we had that information vacuum could ignore the old snapshots on those tables, so long as it ensures that the vacuum process itself can't read anything from those tables (handling the functional index issue Tom mentioned).
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-06-08 22:48:26 | SSI work for 9.1 |
| Previous Message | Brar Piening | 2011-06-08 22:36:44 | Re: smallserial / serial2 |