| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)skype(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Accessing schema data in information schema |
| Date: | 2006-03-22 23:10:08 |
| Message-ID: | 20060322231008.GB9815@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing wrote:
> I guess we can't easily start locking some subarea of a page, say 256
> byte subpage, or just the tuple.
> OTOH it may be possible as we don't need to lock page header for
> sequences as the tuple is updated in place and will not change in size.
Huh, we _can_ lock individual tuples, using LockTuple() (or rather,
heap_lock_tuple). Since the tuple is modified in place, there's no need
to lock the whole page.
> OTOOH, I'm afraid we still need to WAL the whole page, so the savings
> will be marginal.
Huh, why? We can just keep the current WAL logging for sequences, or
something very similar, can't we?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-22 23:48:37 | Re: Accessing schema data in information schema |
| Previous Message | Hannu Krosing | 2006-03-22 22:48:43 | Re: Accessing schema data in information schema |