Postgres Pro
Downloads
Home   >   mailing lists

Thread: Help-PGRES_FATAL_ERROR

Help-PGRES_FATAL_ERROR

From
John Carriel Gomez
Date:
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

Re: Help-PGRES_FATAL_ERROR

From
Jaime Casanova
Date:
On Sun, Aug 7, 2011 at 3:10 PM, John Carriel Gomez
<john.carriel.g@gmail.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);=A0 - ERROR:=A0 in=
valid
> input syntax for type timestamp: "Sun Aug 07 14:59:30.073665 2011 ECT"
> CONTEXT:=A0 SQL statement "insert into "_replicaterminal".sl_confirm
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 (co=
n_origin, con_received, con_seqno)
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 sel=
ect no_id, p_no_id, 0 from
> "_replicaterminal".sl_node
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 where no_id !=3D p_no_id
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 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

--=20
Jaime Casanova=A0 =A0 =A0 =A0=A0 www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitaci=F3n

Re: Help-PGRES_FATAL_ERROR

From
Tom Lane
Date:
Jaime Casanova <jaime@2ndquadrant.com> writes:
> On Sun, Aug 7, 2011 at 3:10 PM, John Carriel Gomez
> <john.carriel.g@gmail.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