| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)enterprisedb(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: idea: global temp tables |
| Date: | 2009-04-29 20:07:11 |
| Message-ID: | 20090429200711.GC6316@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule escribió:
> But question?
>
> about MVCC?
> Is necessary to use MVCC on pg_statistic and some columns from pg_proc?
Right now, we use MVCC everywhere because we have no choice. But there
are some things that would be better off not using MVCC; and indeed we
use a hack to make things that way in certain, very limited cases (see
callers of heap_update_inplace).
Years ago I proposed a patch (search for pg_class_nt and/or pg_ntclass)
that created a catalog for non-MVCC attributes, with an eye on extending
it to more attributes. The use case for those other attributes had
fatal flaws so it went nowhere, but perhaps we can give the idea another
whirl now. For example I think it would be possible to implement
read-only partitions that don't need vacuuming using that idea.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-04-29 20:08:16 | Re: idea: global temp tables |
| Previous Message | Tom Lane | 2009-04-29 19:59:38 | Re: idea: global temp tables |