From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT |
Date: | 2009-04-06 14:35:24 |
Message-ID: | 603c8f070904060735x3a3d87e8k78e52866e72738c6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 6, 2009 at 7:30 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
>> Well, I think I was pretty clear about what I was trying to
>> accomplish. I think there are more people who care about pg_dump
>> output being diffable than there are who need to set ndistinct more
>> accurately than 1 ppm and yet not as an integer. Perhaps if any of
>> those people are reading this thread they could chime in. Otherwise,
>> I will implement as you propose.
>
> I do such diffs pretty often, but I don't think I've *ever* done it on
> catalog tables.. Perhaps it'll come up in the future, but I doubt it.
>
> Stephen
Well the point is when you dump a user table, it will dump this
setting along with it, same as it does now for statistics_target. So
if you diff the DDL you might see differences in rounding. If you
only diff the data, it won't matter unless, as you say, you're dumping
pg_attribute itself.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-04-06 14:49:49 | Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT |
Previous Message | Tom Lane | 2009-04-06 14:06:54 | Re: Auto-delete large objects when referencing row is deleted |