| From: | Berend Tober <btober(at)seaworthysys(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Preserving data after updates |
| Date: | 2005-05-19 16:03:18 |
| Message-ID: | 428CB8C6.1090501@seaworthysys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
>Berend Tober <btober(at)seaworthysys(dot)com> writes:
>
>
>>But after doing a dump of the modified data base, the script created by
>>pg dump wants to recreate the history table as
>>...
>> CONSTRAINT person_name_check CHECK (((last_name IS NOT NULL) OR
>>(first_name IS NOT NULL))),
>>
>>
>
>Hmm, it shouldn't do that ... and in a quick test here I couldn't
>reproduce any such bug. What version of pg_dump are you using?
>
Sorry I failed to specify. Production version is 7.3.1 (change is
hard!), although I origianally worked out the implementation on version
8. I bet that is the problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-19 16:14:58 | Re: Shared memory and FreeBSD's jail() |
| Previous Message | Dawid Kuroczko | 2005-05-19 16:03:09 | Re: Count and Results together |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-05-19 16:22:55 | Re: Contributing |
| Previous Message | Tom Lane | 2005-05-19 15:52:21 | Re: Preserving data after updates |