| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <janwieck(at)Yahoo(dot)com> |
| Cc: | adam(dot)rossi(at)platinumsolutions(dot)com, Ian Turner <vectro(at)pipeline(dot)com>, Martin Christensen <knightsofspamalot-factotum(at)mail1(dot)stofanet(dot)dk>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [Solved] SQL Server to PostgreSQL |
| Date: | 2000-10-15 03:33:42 |
| Message-ID: | 200010150333.XAA22596@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> Tom Lane wrote:
> > Now that you mention it, though, doesn't TOAST break heapam's assumption
> > that char(n) is fixed length? Seems like we'd better either remove that
> > assumption or mark char(n) nontoastable. Any opinions which is better?
>
> Is the saved overhead from assuming char(n) is fixed really
> that big that it's worth NOT to gain the TOAST advantages?
> After the GB benchmarks we know that we have some spare
> performance to waste for such things :-)
Oh, now I get it. Some TOAST values may be out-of line. Can we really
throw char() into TOAST? I guess we can. We have to record somewhere
that we have toasted that tuple and disable the offset cache for it.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-15 04:21:42 | Re: [Solved] SQL Server to PostgreSQL |
| Previous Message | Bruce Momjian | 2000-10-15 03:32:22 | Re: [Solved] SQL Server to PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-10-15 03:39:03 | Re: when does CREATE VIEW not create a view? |
| Previous Message | Bruce Momjian | 2000-10-15 03:32:22 | Re: [Solved] SQL Server to PostgreSQL |