Re: Reduction in WAL for UPDATEs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
Cc: "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Kenneth Marshall" <ktm(at)rice(dot)edu>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Reduction in WAL for UPDATEs
Date: 2007-03-28 16:40:01
Message-ID: 3849.1175100001@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> writes:
> Btw: Do we consider the existance of toasted columns in the seq-scan
> cost estimation ?

Not at present. There was some discussion of this but it seems like
a fair amount of work --- we don't currently track statistics on how
many of a column's entries are toasted or how big they are. For that
matter it would be entirely unreasonable to pin the cost on "seq scan";
you'd need to look in close detail at exactly where and how the Vars get
used, and distinguish simply copying a Var from actual use of its value.
The planner is mostly uninterested in the evaluation costs of plan node
targetlists at the moment, and IIRC that's something not so easily
changed...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2007-03-28 16:54:02 Re: CREATE INDEX and HOT - revised design
Previous Message Simon Riggs 2007-03-28 16:37:03 Re: Patch queue concern