Re: Help-PGRES_FATAL_ERROR

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: John Carriel Gomez <john(dot)carriel(dot)g(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Help-PGRES_FATAL_ERROR
Date: 2011-08-08 15:08:07
Message-ID: 25829.1312816087@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jaime Casanova <jaime(at)2ndquadrant(dot)com> writes:
> On Sun, Aug 7, 2011 at 3:10 PM, John Carriel Gomez
> <john(dot)carriel(dot)g(at)gmail(dot)com> wrote:
>> Please help I can not replicate with Slony
>> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>> PGRES_FATAL_ERROR select "_replicaterminal".storeNode_int(1, 'Nodo
>> Maestro'); select "_replicaterminal".enableNode_int(1); - ERROR: invalid
>> input syntax for type timestamp: "Sun Aug 07 14:59:30.073665 2011 ECT"
>> CONTEXT: SQL statement "insert into "_replicaterminal".sl_confirm
>> (con_origin, con_received, con_seqno)
>> select no_id, p_no_id, 0 from
>> "_replicaterminal".sl_node
>> where no_id != p_no_id
>> and no_active"
>> PL/pgSQL function "enablenode_int" line 32 at SQL statement

> what do you have in timezone in postgresql.conf? certainly, the
> timestamp format looks odd

I think the format is OK but the receiving machine doesn't recognize
"ECT" as a timezone abbreviation. So, there's something different in
the timezone abbrevation configurations on the two machines.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message ai 2011-08-08 15:31:30 Re: BUG #6154: wrong result with nested left-joins
Previous Message ai 2011-08-08 15:08:05 Re: BUG #6154: wrong result with nested left-joins