Thanks for the response.
For anyone who is interested, I fixed the problem as follow:
On both the Master and Slave Postgres, I added the following lines to the
"Default" file that is inside the "timezonesets" folder and saved.
WIB 25200 # Waktu Indonesia Barat
# (Asia/Jakarta)
# (Asia/Pontianak)
WIT 32400 # Waktu Indonesia Timur (caution: this used to mean 25200)
# (Asia/Jayapura)
WITA 28800 # Waktu Indonesia Tengah
# (Asia/Makassar)
Then, in the "postgresql.conf" file, I uncommented and saved
timezone_abbreviations = 'Default'
The default "timezone_abbreviations" is probably "Default" but I
uncommented just for good measure lol.
Finally, I restarted both postgres services.
If you do a
SELECT * FROM pg_timezone_abbrevs
You will see the "MIB" abbreviation that was not there before the
modifications of the files.
On Fri, Jul 19, 2024 at 7:36 AM Steve Singer <[email protected]> wrote:
> On Fri, 19 Jul 2024, Sung Hsin Lei via Slony1-general wrote:
>
>
> When I try that locally into a table without slony I get the error
>
> ~~~
> create temp table c (a timestamptz);
> CREATE TABLE
> template1=# insert into c values('Fri July 19 12:48:20.754251 2024 WIB');
> ERROR: invalid input syntax for type timestamp with time zone: "Fri July
> 19
> 12:48:20.754251 2024 WIB"
> ~~~
>
> Have you tried running slon with a different timezone?
>
> Maybe
> export TZ=UTC
> into the environment before starting slon(though I haven't tried this)
>
> Steve
>
>
>
> > Has anyone experienced a timezone issue with Asia/Jakarta?
> > I'm getting an "Invalid input syntax for type timestamp with time zone"
> when slony inserts into sl_confirm table. Apparently,
> > it does not like the WIB in "Fri July 19 12:48:20.754251 2024 WIB"
> >
> > Any way of getting around this without changing the timezone in Postgres?
> >
> >
> > Thanks.
> >
> > Sung Hsin
> >
> >
> >
> >
>
_______________________________________________
Slony1-general mailing list
[email protected]
https://lists.slony.info/cgi-bin/mailman/listinfo/slony1-general
