Re: date_trunc check constraint causes errors when restoring in a db with a different time zone

From: Anthony Manfredi <amanfredi(at)gilt(dot)com>
To: Denish Patel <denish(at)omniti(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: date_trunc check constraint causes errors when restoring in a db with a different time zone
Date: 2011-01-18 16:08:42
Message-ID: AANLkTikxJ5DAd-xUcr6EX7Nmh2-8qAU9pAjrt7M9V1c8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks, that is helpful. There was a separate reason it didn't appear
to be happening before the 8.4 upgrade.
I couldn't find this mentioned in the documentation anywhere. Should
it be included in the pg_restore section?

-Anthony

On Sun, Jan 16, 2011 at 11:06 AM, Denish Patel <denish(at)omniti(dot)com> wrote:
> Anthony,
> As per my knowledge, this can't work on pg84 dump/restore too. You should
> match timezone on restoring database with the dump database to load it
> successfully. You can set at user level or database level.
>  On restoring database:
>    ALTER DATABASE test_db_2 SET TIMEZONE TO 'UTC';
>     OR
>    ALTER USER postgres SET TIMEZONE TO 'UTC';
> Hope , it will help.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Popowich 2011-01-18 16:30:04 BUG #5842: Memory leak in PL/Python when taking slices of results
Previous Message Dave Page 2011-01-18 15:11:06 Re: BUG #5791: Tables are not viewing through pgadmin