| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Jorge Godoy" <jgodoy(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org>, "Joe Conway" <mail(at)joeconway(dot)com>, "Stefan Schwarzer" <stefan(dot)schwarzer(at)grid(dot)unep(dot)ch> |
| Subject: | Re: Crosstab Problems |
| Date: | 2007-10-19 10:48:22 |
| Message-ID: | 87wstjmlc9.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-patches |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> 3. Throw a NOTICE or WARNING (hopefully only one message not repeated
> ones) if NULL rowid is seen, then ignore the row.
From my experience with OLTP I don't like this one. A warning for DML is
effectively the same as an error if you're running thousands of queries per
minute. The logs fill up and even if you filter the logs it imposes extra
run-time overhead. You end up having to avoid the warning just as if it had
been an error.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2007-10-19 10:52:07 | Re: Stalled post to pgsql-bugs |
| Previous Message | Alban Hertroys | 2007-10-19 10:41:24 | Re: Abbreviation list |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gokulakannan Somasundaram | 2007-10-20 03:54:07 | Re: Including Snapshot Info with Indexes |
| Previous Message | Stefan Schwarzer | 2007-10-19 08:45:16 | Re: Crosstab Problems |