From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Daniel Cristian Cruz <danielcristian(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Memory usage after upgrade to 9.2.4 |
Date: | 2013-04-25 02:24:22 |
Message-ID: | 517893D6.60600@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/24/2013 11:20 AM, Daniel Cristian Cruz wrote:
> I've done an explain analyze under the test environment, and there is no
> aggressive memory usage.
>
> So I dropped the database in the new cluster and restored a fresh dump
> from production (in theory, that's the difference between the two
> environments).
>
> Some minutes after I got an answer: after a dump / restore, there is no
> problem. The same cluster just a dump/restore.
>
> Since I had no idea on what is the problem, and the structure from the
> dump of the bad database is equal to the dump from the production (it
> differs only in check constraints where "((turma.situacao)::text = ANY
> ((ARRAY['Aguardando Atualização'::character varying, 'Em
> Andamento'::character varying])::text[])))" became
> "((turma.situacao)::text = ANY (ARRAY[('Aguardando
> Atualização'::character varying)::text, ('Em Andamento'::character
> varying)::text])))"), how can I report a issue in pg_upgrade?
The bug reporting page is here:
http://www.postgresql.org/support/submitbug/
>
> Thanks, Adrian, Tomas and Tom. It's a specific issue, it's on backup
> until May, 1st. Until there, if someone would like to know something
> about it, just ask me, I would like to help removing an issue.
>
>
>
> --
> Daniel Cristian Cruz
> クルズ クリスチアン ダニエル
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Konoplev | 2013-04-25 02:44:25 | Re: Replication terminated due to PANIC |
Previous Message | Adrian Klaver | 2013-04-25 02:21:18 | Re: Regarding template1 database |