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
Tim Uckun writes:
>> Possibly the table's never been ANALYZEd ... do you have autovacuum
>> enabled?
> I do have autovacuum enabled and I am running 8.4
Hmm, autovacuum *should* have been keeping track of things for you,
but it might still be worth doing a manual ANALYZE against that table
to se
I just tried and it works. Thank you very much.
-Message d'origine-
De : Alex Hunsaker [mailto:bada...@gmail.com]
Envoyé : vendredi 14 janvier 2011 07:33
À : Julien Demoor
Cc : pgsql-bugs@postgresql.org
Objet : Re: [BUGS] BUG #5835: PL/Python crashes
On Thu, Jan 13, 2011 at 06:57, Julien
> Hmm, autovacuum *should* have been keeping track of things for you,
> but it might still be worth doing a manual ANALYZE against that table
> to see if the estimated rowcount changes. If not, you'll need to raise
> the statistics target for that column (and again ANALYZE).
>
I started a manual
>
> Hmm, autovacuum *should* have been keeping track of things for you,
> but it might still be worth doing a manual ANALYZE against that table
> to see if the estimated rowcount changes. If not, you'll need to raise
> the statistics target for that column (and again ANALYZE).
The analyze finish
