| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Alvaro Herrera" <alvherre(at)atentus(dot)com> |
| Cc: | "Rod Taylor" <rbt(at)zort(dot)ca>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] [SQL] 16 parameter limit |
| Date: | 2002-04-16 03:49:30 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOOECGCCAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches pgsql-sql |
> > Anyway, how does one measure the perfomance impact of such a change?
> > By merely changing the constant definition, or also by actually using
> > long identifiers? I can do that if it's of any help, for various values
> > perhaps.
>
> I think I would measure disk size change in a newly created database,
> and run regression for various values. That uses a lot of identifier
> lookups.
With schemas, maybe there'd be less name lookups and comparisons anyway,
since there's more reliance on oids instead of names?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-04-16 03:51:31 | Re: ANSI Compliant Inserts |
| Previous Message | Bruce Momjian | 2002-04-16 03:44:16 | Re: [PATCHES] [SQL] 16 parameter limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-04-16 03:51:31 | Re: ANSI Compliant Inserts |
| Previous Message | Bruce Momjian | 2002-04-16 03:44:16 | Re: [PATCHES] [SQL] 16 parameter limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2002-04-16 03:52:16 | Re: [SQL] 16 parameter limit |
| Previous Message | Bruce Momjian | 2002-04-16 03:44:16 | Re: [PATCHES] [SQL] 16 parameter limit |