| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Nullability patch take 2 |
| Date: | 2002-04-01 05:21:22 |
| Message-ID: | 002601c1d93d$10966a10$0200a8c0@SOL |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> Checked and applied. I made one nontrivial change --- for anything on
> which there's a syscache, it's a lot easier (and faster) to use
> SearchSysCacheCopy to get a tuple to update than it is to do a heapscan.
> The syscache will either have the tuple already, or will get it with an
> indexscan --- either way wins over a heapscan when the catalog is at
> all large.
Cool. Question - are all these little tricks documented somewhere? I'm
considering improving the source code section of the manual to include
HOWTOs for coding with Postgres - might attract more patches. I mean, if
I'd been given a list of all these things, with implementation examples,
beforehand it'd make my life a lot easier.
BTW - would you be able to comment on my earlier email regarding hints for
letting the executor handle rangevars from stored procedures???
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-01 05:42:10 | Re: Nullability patch take 2 |
| Previous Message | Tom Lane | 2002-04-01 04:41:33 | Re: Nullability patch take 2 |