Re: Logical Replication 08P01 invalid memory alloc request size 1095736448

2025-07-06 Thread Soni M
Thanks Tom, really appreciate it. On Sun, Jul 6, 2025 at 10:12 PM Tom Lane wrote: > Soni M writes: > > We just do patch updates from 15.12 to 15.13, restart Logical Master and > > then Logical Replica, and suddenly Logical replication stops working. > > Streaming replica

Re: Logical Replication 08P01 invalid memory alloc request size 1095736448

2025-07-06 Thread Soni M
m_exit callbacks to make",,,,,"","logical replication worker",,0 DEBUG,0,"proc_exit(1): 1 callbacks to make","","logical replication worker",,0 DEBUG,0,"exit(1)","","logical replication worke

Logical Replication 08P01 invalid memory alloc request size 1095736448

2025-07-06 Thread Soni M
will begin using saved snapshot.","START_REPLICATION SLOT ""_subscription"" LOGICAL 33D45/373C2D98 (proto_version '3', publication_names '""_publication""')",,,"_subscription","walsender",,0 Checking at error code 08P01 is protocol_violation. Is there any idea on what causing this and how to resolve ? -- Regards, Soni Maula Harriz

Re: could not fsync file ""pg_wal/xlogtemp.23229"": Input/output error

2021-01-15 Thread Soni M
Fix it already, so it was the SAN and vmware issue. Thanks Everyone. On Fri, Jan 15, 2021 at 4:40 PM Soni M wrote: > More disk space now available, but still the error happens and postgres > won't start. > I think it could be corrupted shared buffers, as stated on the log &

Re: could not fsync file ""pg_wal/xlogtemp.23229"": Input/output error

2021-01-15 Thread Soni M
13 +0700, Soni M wrote: > > We filled out the wal archive disk, and then those messages appear > > > > [...]PANIC,58030,"could not fsync file ""pg_wal/xlogtemp.3510"": > Input/output error" > > > > And now I cannot start postgres > >

could not fsync file ""pg_wal/xlogtemp.23229"": Input/output error

2021-01-15 Thread Soni M
ted by signal 6: Aborted","" 2021-01-15 03:04:19.979 CST,,,23226,,6001550d.5aba,3,,2021-01-15 02:40:45 CST,,0,LOG,0,"aborting startup due to startup process failure","" 2021-01-15 03:04:20.041 CST,,,23226,,6001550d.5aba,4,,2021-01-15 02:40:45 CST,,0,LOG,0,"database system is shut down","" Any idea to solve this ? -- Regards, Soni Maula Harriz

Encrypted connection SQL server fdw

2020-01-10 Thread Soni M
Hi All, currently I'm trying to configure postgres (on centos) to load data from MS SQL server (on windows server) on an encrypted connection. Trying with tds_fdw, but found that it doesn't support encrypted connection. Is there any solution to this? Thanks, Soni.

Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184

2019-04-22 Thread Soni
I did not re-initdb, just use the old pgdata. I also did not recreate current database. Some of the database has value 1 for lanvalidator, some has 2247. I'll check with the team how the lanvalidator got 1 for the value. I will report back here. Thanks, Soni. On 23/04/2019 10:51, Tom

Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184

2019-04-22 Thread Soni
Fix it, change the lanvalidator value of 1 to the value of fmgr_c_validator. Thanks a lot Tom, that was fantastic. Not sure how the lanvalidator value changed to 1. Thanks, Soni On 23/04/2019 10:39, Soni wrote: Here it is: select * from pg_language;  lanname  | lanowner | lanispl

Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184

2019-04-22 Thread Soni
|    1 | (4 rows) Thanks, Soni On 23/04/2019 10:31, Tom Lane wrote: Soni writes: Here's the backtrace. Please let me know if it helps. #4  OidFunctionCall1Coll (functionId=functionId@entry=1, collation=collation@entry=0, arg1=arg1@entry=75471) at fmgr.c:1325 hm, there's "funct

Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184

2019-04-22 Thread Soni
  comment ---+-+---+-  uuid-ossp | 1.1 |   | generate universally unique identifiers (UUIDs) (1 row) -bash-4.2$ ls /usr/pgsql-10/lib/uuid-ossp.so /usr/pgsql-10/lib/uuid-ossp.so Thanks, Soni

Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184

2019-04-22 Thread Soni
ag=0x7ffcd9091930 "") at pquery.c:799 #18 0x0071aa13 in exec_simple_query (query_string=out>) at postgres.c:1122 #19 0x0071bd0c in PostgresMain (argc=, argv=, dbname=, username=) at postgres.c:4117 #20 0x0047b246 in BackendRun (port=0x1098a20) at postmaster.c:44

Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184

2019-04-22 Thread Soni
I install the contrib module from the postgres repo using yum install. creating extension run as postgres superuser. Thanks, Soni On 22/04/2019 21:05, Adrian Klaver wrote: On 4/21/19 9:14 PM, Soni wrote: Hello All, CentOS Linux release 7.5.1804 (Core) Postgres 10.7. When "create exte

cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184

2019-04-21 Thread Soni
, fmgr.c:184 2019-04-22 02:41:53.323 UTC [10305] XX000STATEMENT:  create extension "uuid-ossp" ; I tried reinstall contrib module and even all postgres component, but still no luck. Try restarting the server also but no luck. Any idea how to resolve this ? Thanks, Soni

Re: PG10 declarative partitioning that allow null value

2019-04-15 Thread Soni
I think it's better to had list partitioning of true/false based on (int_key_column is null) CREATE TABLE partitioned_table_name (like table_name) partition by list ((int_key_column is null)); On 16/04/2019 9:37, Soni wrote: Hello All, currently we are planning to migrate inheri

PG10 declarative partitioning that allow null value

2019-04-15 Thread Soni
significantly due to the process of counting the number of digits ? or is there any better workaround for this ? Thanks, Soni.