| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE lock level |
| Date: | 2013-06-04 22:29:41 |
| Message-ID: | 51AE6A55.702@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 02/06/2013 13:47, Kevin Grittner wrote:
> That's good as far as it goes, but there's another major reason for
> wanting the capability. There are cases where, due to dirty
> converted data or late recognition of the need for a constraint
> there is existing data which violates the constraint. Being able
> to add a constraint to protect against creating additional bad data
> before all the existing problems are cleaned up can be valuable.
Yeah, that's a valid use case.
Anyway, you seem to know more about this than I do and your English is
better, so I'll leave it up to you. I just hope we can get this change
into the next minor release so I'd be the last person to suffer from the
misinformation that's currently in the documentation.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | eggyknap | 2013-06-05 03:05:57 | Minor quibble with description of WINDOW clause |
| Previous Message | Kevin Grittner | 2013-06-02 11:47:38 | Re: ALTER TABLE lock level |