| From: | nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) |
|---|---|
| To: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | default attstattarget |
| Date: | 2002-07-20 04:42:22 |
| Message-ID: | 20020720044222.GA25549@klamath.dyndns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Hi all,
The attached patch implements the pg_attribute.attstattarget scheme
discussed on -hackers today. A value of "-1" in this column indicates
that ANALYZE should use the compiled-in default value. This allows
pg_dump to record and restore any changes made by the DBA to this
value using ALTER TABLE ALTER COLUMN SET STATISTICS.
I made another small behavioral change: IMHO, silently changing
stat target values we deem inappropriate (< 0, > 1000) without
warning the user is a bad idea. I changed the < 0 case to be a
elog(ERROR) and added an elog(WARNING) for the > 1000, and
documented the upper bound.
Unless anyone sees any problems, please apply.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
| Attachment | Content-Type | Size |
|---|---|---|
| attstat-3.patch | text/plain | 26.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-07-20 04:58:35 | Re: Fix for regression caused by heap tuple header changes |
| Previous Message | Tom Lane | 2002-07-20 03:26:58 | Re: lock listing |