| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <wieck(at)debis(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] type coerce problem with lztext |
| Date: | 2000-02-27 21:35:54 |
| Message-ID: | 16771.951687354@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
wieck(at)debis(dot)com (Jan Wieck) writes:
> rulename | length | octet_length
> ----------------+--------+--------------
> _RETv1 | 64677 | 7440
> The view v1 is a simple 'SELECT * FROM t1' and t1 is a table
> of 220 columns with the same names and types as nearly all
> attributes of the system catalogs. Makes me feel comfortable.
Wow, better than 8-to-1. I guess you'd expect good compression on that,
considering the very repetitive nature of the targetlist node string.
Have you tried something with a long, boring WHERE-clause?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-02-27 22:02:02 | Re: [HACKERS] type coerce problem with lztext |
| Previous Message | Don Baccus | 2000-02-27 21:30:28 | Re: [HACKERS] type coerce problem with lztext |