From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jeffrey Baker" <jwbaker(at)gmail(dot)com> |
Cc: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: proposal for smaller indexes on index-ordered tables |
Date: | 2008-06-25 03:03:16 |
Message-ID: | 10744.1214362996@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jeffrey Baker" <jwbaker(at)gmail(dot)com> writes:
> I guess nobody has any interest in my proposal, only in the departure of my
> described experience from expected behavior :-(
Well, we certainly should try to understand the unexpected behavior
in detail before we consider solutions. Per Sir A.C. Doyle, it is a
capital mistake to theorize in advance of the data.
(It's probably also worth noting that this community's historical
interest has not been in read-only or even read-mostly data. We'd
not be willing to pay all that MVCC overhead if we thought we were
just a warehouse of static data. If that's what you want, maybe
you need some other DBMS.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | daveg | 2008-06-25 03:57:19 | Re: [HACKERS] Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
Previous Message | Tom Lane | 2008-06-25 02:41:07 | Re: [HACKERS] Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |