Re: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=UNOFFICIAL]

be a help for you, although it's not clear what is happening yet. [1] https://www.postgresql.org/message-id/CAFh8B%3DmozC%2Be1wGJq0H%3D0O65goZju%2B6ab5AU7DEWCSUA2OtwDg%40mail.gmail.com regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=UNOFFICIAL]

to know that. I think that relationship has not been explained here. Could you explain the routes and timings that WAL files are copied between the servers? regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: walreceiver fails on asynchronous replica [SEC=UNOFFICIAL]

e situation actually arose. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.

At Wed, 29 Nov 2023 18:29:15 +0100, Alvaro Herrera wrote in > The code in master is completely different (it uses pg_pread rather than > seek + read): it does test for errno and reports accordingly. > > So, nothing to do here. Oops! Thank you and sorry for the noise. regards.

Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.

ereport(ERROR, > (errcode_for_file_access(), > errmsg("could not access status of transaction %u", xid), > errdetail("Could not read from file \"%s\" at offset %d: %m.", regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: How does pg parse 'select '(1,2)''

target_el: a_expr a_expr: c_expr c_expr: implicit_row implicit_row: '(' expr_list ',' a_expr ')' expr_list: a_expr | expr_list ',' a_expr regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Understanding pg_stat_io.evictions

py operations.). > As far as I understand this, a ring buffer is used in this case. Do I miss > something? Maybe you're confusiong it with bulk-read cases? regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Bogus temp file reporting?

able, you'll find that pg_stat_database.temp_bytes doesn't increase at all. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Problematic enforcement of "ERROR: functions in index predicate must be marked IMMUTABLE"

o the system, not vice versa. If you break your promise, > you get to keep both pieces of whatever trouble ensues. I agree to you, as I mentioned a-bit-too-late message.. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Problematic enforcement of "ERROR: functions in index predicate must be marked IMMUTABLE"

At Tue, 11 Jul 2023 10:14:29 +0900 (JST), Kyotaro Horiguchi wrote in > At Sun, 9 Jul 2023 14:22:37 +, Avi Weinberg wrote in > > Hi, > > > > If you attempt to create an index based on function that is not IMMUTABLE > > you will get an exception "ERROR: f

Re: Problematic enforcement of "ERROR: functions in index predicate must be marked IMMUTABLE"

om entering an inconsistent state, at least on the surface. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: PostgreSQL 13 - Logical Replication - ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected

hardware problems or changes of firewall or networking setup of the OS. I think it would be good idea to check for them first. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Logical replication fails when adding multiple replicas

char *syncslotname, Size szslot) { snprintf(syncslotname, szslot, "pg_%u_sync_%u_" UINT64_FORMAT, suboid, -relid, GetSystemIdentifier()); +relid, PgStartTime); } /* regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: How could I elog the tupleTableSlot to the fronted terminal?

stake It's not clear to me what the terminal means, but can you find it in server log instead? reagrds. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Segmentation fault on RelationGetDescr in my first extension

table does not exist. # I modified contrib/passwordcheck that way and saw RelationGetDescr() # doesn't get segv in the shown context. I guess the segv comes from another place, or something else has broken memory until there. but anyway more information is needed for people to diagnose your si

Re: How to check stream replication latest history status

the primary. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: AW: Reducing bandwidth usage of database replication

ng_delay = 130s > max_standby_archive_delay = 45s > wal_receiver_status_interval = 600s > wal_receiver_timeout = 1200s > wal_receiver_timeout = 65s > recovery_min_apply_delay = 600s > > The random values were to see which setting is limiting if I got above the > 30s limit. regards.

Re: Streaming wal from primiry terminating

y, or a case where restore_command on the standby fetches WAL files from pg_wal on the primary instead of its archive. Both are not normal operations. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Unable to archive logs in standby server

witch is to arrange for the last WAL segment file written > during the backup interval to be ready to archive. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: recovery_command has precedence over phisical slots?

very beyond the slot LSN is the db2's restore_command (I guess) points to db1's archive. If db2 had its own archive directory or no archive (that is, restore_command is empty), archive recovery stops at (approximately) the slot LSN and replication will start from there (from the beginning of the segment, to be exact). regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Unable to start replica after failover

s nowhere other than there) and it must be in pg_wal directory unless someone removed it. Thus, I think we need the exact steps you and your system took after the failover happened about postgresql. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Unable to start replica after failover

see what is happning there, since you didn't give us sufficient information on the configuration and exact steps. But roughly it looks like shuffling/mixing of WAL files among several systems (or WAL archives) with different histories. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: General Inquiry

rver. If they are unexpected incoming connections, one possibility is that something like health-check or keep alive thing is having a wrong interval setting. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: help for pg_wal issue

At Tue, 28 Jun 2022 16:28:31 +0900 (JST), Kyotaro Horiguchi wrote in > At Mon, 27 Jun 2022 12:28:18 +0200, Laurenz Albe > wrote in > > You forgot to tell us how exactly you are performing that backup. > > Yeah, but Google told me that Veritas may complain with that

Re: help for pg_wal issue

tps://www.postgresql.org/docs/devel/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP If you still see the point, feel free to ask further here but with showing exactly how you are peforming that backup:p regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Any way to understand state after data corruption failures during startup.

7 13:30:52.493 JST PANIC: incorrect resource manager data checksum in record at 0/360 At least in this case, there's no trace of a server-stop due to WAL corruption left behind other than in server log. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: message log merge (streaming replication)

nded behaviour? > > It's not typical behaviour, but I suppose it's conceivable someone designed > such a setup for some reason. If the node-02 is a replica of the node-01 or vise-versa, and the log file is in $PGDATA, it's possible that pg_basebackup (or just cp) copies in the server log file to the replica. In that case, the first half of the log file of the day of taking the backup is taken over from the primary and the last half differs. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: FATAL: could not receive timeline history file from the primary server: ERROR: could not open file "pg_wal/0000000x.history": No such file or directory

ove some history files on primary, do not remove them for between the TLIs of primary and standby. > slave node has recovery.conf file and include primary_con_info informations. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: SQL state: 42601. Execption handling.

oesn't catch it.) =# select f1(); ERROR: column "d" does not exist (Caught by SQL parser executed at runtime) =# CREATE OR REPLACE FUNCTION f2() RETURNS void AS $$ begin select p.result from dbo.func() p into v_result; end ; $$ LANGUAGE plpgsql; ERROR: "v_result"

Re: pg_create_logical_replication_slot in DB1 is blocked by a session in DB2

| > > > The blocked and blocking sessions are on two different DBs > > datid|datname |pid |leader_pid|usesysid|usename|application_name > |cl > -|-|-|--||---|--|-- > 16408|db1 |13405| | 16394|test99 | > |10 > 16407|db2 | 8602| |29429933|service_con_9 |PostgreSQL JDBC > Driver|10 > > Thank you regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: PSQL bug?

This probably means the server terminated abnormally > before or while processing the request. > The connection to the server was lost. Attempting reset: Succeeded. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Postgres Wal Full

reate regular file '/archive/00010001': No such > file or directory regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: ssl_crl_file Certificate Revocation List doesn't work for postgresql 11

e next minor releases. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: ssl_crl_file Certificate Revocation List doesn't work for postgresql 11

ropose change the rephrase as "SSL client certification revocation list" as attached. regards. -- Kyotaro Horiguchi NTT Open Source Software Center diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index ab617c7b86..4ac617615c 100644 --- a/doc/src/sgml/con

Re: ssl_crl_file Certificate Revocation List doesn't work for postgresql 11

entries are also checked if the file > ~/.postgresql/root.crl exists (%APPDATA%\postgresql\root.crl on > Microsoft Windows). regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: ssl_crl_file Certificate Revocation List doesn't work for postgresql 11

ed to revoke was not server.crt but postgresql.crt. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: WAL File Recovery on Standby Server Stops Before End of WAL Files

ure" indicate > a problem with the WAL file? Actually the message says that some trouble happend while reading file but that happens always at the end of wal. We might need a bit more detailed message about the trouble in higher debug level messages. > Anyway, it looks like I need to restore the standby server from a new backup. > Thank you both for your help. Unfortunately I think so, too. > Sincerely, > -Les -- Kyotaro Horiguchi NTT Open Source Software Center

Re: WAL File Recovery on Standby Server Stops Before End of WAL Files

hat I'm expecting to see is an error message from pg_waldump before the end of the file. It would be the immediate cause of the problem. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Postgresql 11: terminating walsender process due to replication timeout

scriber. > On Fri, Sep 10, 2021 at 9:26 AM Kyotaro Horiguchi > wrote: > > > At Thu, 9 Sep 2021 16:06:25 +0900, Abhishek Bhola < > > abhishek.bh...@japannext.co.jp> wrote in > > > sourcedb:~$ postgres --version > > > postgres (PostgreSQL) 11.6 > >

Re: Postgresql 11: terminating walsender process due to replication timeout

nds, subscriber doesn't send a response in the timeout window. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Postgresql 11: terminating walsender process due to replication timeout

replication worker was initialized in each loop checking if a > message was received or not, causing wal_receiver_timeout to be ignored > in basically any logical replication deployments. This also broke the > ping sent to the server when reaching half of wal_receiver_timeout. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: oldest WAL files not removed

areful not to remove files with its substantial contents. This is why I said "In any case, no WAL files ought to be manually removed." regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: oldest WAL files not removed

ed file to be used in future, and the "newest" file is the currently written one. If so, the reason that the oldest-in-timestamp file is still there is it is still waiting to be used. Even if you removed the to-be-used-in-future files, such files would increase to the same extent according to the setting of min_wal_size. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Removing a subscription that does not exist

ot exist > Time: 23.648 ms > > I did try deleting it directly from the pg_subscription table but that > failed with a permission denied error.  My suspicion is that's because > of the RDS environment. > > What else can I try to remove this old non-functional subscription? Thus you need to log in to the databse OID=14313 to manipulate on the subsciption metro. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: wal_keep_segments and max_wal_size

is greater than max_wal_size - [*1], that is, 43 16MB-files, max_wal_size would be overflown before XLOG-triggered checkpoint caused by max_wal_size starts. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: some questions regarding replication issues and timeline/history files

n, run pg_rewind like the follows, for example. $ pg_rewind --target_pgdata= --target-server='connstr to B' pg_rewind: servers diverged at WAL location 0/360 on timeline 1 pg_rewind: rewinding from last common checkpoint at 0/260 on timeline 1 regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: "invalid contrecord" error on replica

rimary. After some time the primary reaches A100 but the first record in the segment is of course disagrees with the history of the secondary. 1: https://www.postgresql.org/message-id/CBDDFA01-6E40-46BB-9F98-9340F4379505%40amazon.com regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: PITR for an only object in postgres

for logical replication, but perhaps we don't have that. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Right way to restore logical replication

on. This allows the newly created publication to work. Also you can drop the subscription, then manually fix the subscriber table to sync with the publisher table, then create a new subscription using WITH (copy_data = false); regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Problem with ssl and psql in Postgresql 13

At Thu, 24 Dec 2020 11:54:32 -0500, Tom Lane wrote in > I wrote: > > Kyotaro Horiguchi writes: > >> The attached the first patch does that. > > > +1, it seems like a clear oversight that the GSSENC patches didn't adjust > > these messages. The reason SS

Re: Problem with ssl and psql in Postgresql 13

state machine so that it doesn't do that at all, but instead skips SSL > establishment when GSS is already active via an explicit test, rather > than munging the state variables. It could make things simpler, but I'm not sure though. Anyway the states are needed since PQconnectPoll(the s

Re: Problem with ssl and psql in Postgresql 13

he following in the server log in that case. LOG: hostssl record cannot match because SSL is disabled HINT: Set ssl = on in postgresql.conf. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Date Format 9999-12-31-00.00.00.000000

e translated on-the-fly. I'm not sure which is efficient in that case. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: How bad is using queries with thousands of values for operators IN or ANY?

At Tue, 1 Sep 2020 18:46:01 +0200, Pavel Stehule wrote in > nice :) thanks ;p regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: How bad is using queries with thousands of values for operators IN or ANY?

77.205 rows=10001 loops=1) Hash Cond: (t1.a = "*VALUES*".column1) -> Seq Scan on t1 (cost=0.00..1443.00 rows=10 width=8) (actual time=0.017..23.540 rows=10 loops=1) -> Hash (cost=125.01..125.01 rows=10001 width=4) (actual time=13.786..13.788 rows=10001

Re: 12.3 replicas falling over during WAL redo

sc: INSERT_LEAF off 48, blkref #0: rel > 16605/16613/60529051 blk 6501 There must be a record for the page 6501 conveying FPW after the last checkpoint. If it is not found, something wrong on deciding whether to attach FPW. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: 12.3 replicas falling over during WAL redo

ere flushed out during a vacuum after the last checkpoint and full-page-writes didn't restored the page to the state before the index-item deletion happened(that is, if full_page_writes were set to off.). (If it found to be the cause, I'm not sure why that didn't happen on 9.5.) regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Questions about Logical Replication - Issue ???

n (copy_data = false), I am > able to replicate the new record. As you know, initial table copy happens defaultly at subscription creation (the COPY command in the above log lines was doing that). If you are sure that the publisher table is in-sync with the subscriber one, you can use copy_data=fal

Re: A query in Streaming Replication

g into the next timeline. I don't have an idea at hand of how this can be relevant to the reusability of the old master.. > > peer DB which comes back as slave is unable to sync when this happens.. > > Please suggest if this happens in any scenario and how to overcome this. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Conflict with recovery on PG version 11.6

fter version upgrade. > > This is the reason why I am very keen to find out real cause for the conflict. FWIW in case you haven't tried yet, if you could find a DETAILS: line following to the ERROR: canceling.." message in server log, it would narrow the possibility. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: canceling statement due to conflict with recovery after pg_basebackup

relkind='c' then 'composite type' > when c.relkind='S' then 'sequence' >else c.relkind::text > end ::char(14) as "type" > from >pg_class c >left join pg_namespace n on n.oid = c.relnamespace >left join pg_tablespace t on t.oid = c.re

Re: How to recover from compressed wal archieve in windows

> > > > https://www.7-zip.org/ > > > > Not sure how well it works with redirects/pipes. > > I'm no windoze guru, so I don't know about that, but you may have a look at: > > http://gnuwin32.sourceforge.net/packages/gzip.htm Or cygwin or mingw? http://www.mingw.org/ regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: How to recover from compressed wal archieve in windows

lled with multiple WAL records. The "full page image", which is described to be compressed by the parameter, is a part of WAL record. A WAL file is filled with maybe-compressed WAL records and has the same size in the case where wal_compression is on. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Configuring more than one hot standby server

+- [standby 3] LSN = x - 6 after : [old standby 2] -+- [standby 1] +- [standby 3] That is the same for the case of quorum-mode synchronous standbys setting. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Hot and PITR backups in same server

data directory created using > pg_basebackup. > All WAL segments from master server after pg_basebackup should saved > in backup server and should be used for PITR recovery when needed. > > How to use hot standby server for this ? > > Or should separate cluster in 5433 port created and pg_rewind or > something other used for PITR. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails

old WAL segments, > which increases the chance for "pg_rewind" to succeed. So this is one effective way to reduce the chance to lose required WAL (segment) files. On PG12, an easy way to automatically restore all required WAL files would be restoring the WAL file every time pg_rewind comp

Re: PostgreSQL-12 replication failover, pg_rewind fails

So you seem to need to restore the required WAL files from archive or the current master. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: walreceiver termination

ding the close-connection message. If it happens constantly, routers or firewalls between the primary and standby may be discarding sessions inadvertantly. I'm not sure how ZFS can be involved in this trouble, though. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: pg_restore: could not close data file: Success

At Thu, 16 Apr 2020 14:40:09 +0900, Michael Paquier wrote in > On Thu, Apr 16, 2020 at 12:08:09PM +0900, Kyotaro Horiguchi wrote: > > I'm surprised to find an old thread about the same issue. > > > > https://www.postgresql.org/message-id/20160307.174354.251049

Re: pg_restore: could not close data file: Success

se properly passes-through the error code from gzclose, so it is enought that the caller should recognize the difference. Please find the attached. regards. -- Kyotaro Horiguchi NTT Open Source Software Center diff --git a/src/bin/pg_dump/compress_io.c b/src/bin/pg_dump/compress_io.c index 1417401086..3a

EINTR while resizing dsm segment.

;& !(ProcDiePending || QueryCancelPending)); But not for ftruncate and write. Don't we need to protect them from ENTRI as the attached? -- Kyotaro Horiguchi NTT Open Source Software Center >From 590b783f93995bfd1ec05dbcb2805a577372604d Mon Sep 17 00:00:00 2001 From: Kyotaro Horiguchi Date: Thu, 2

Re: It is possible to force periodically switch xlog?

quot;archive_mode=off". > > I'm not sure what the point of switching the WAL segment would be with > archive_mode=off. > > What are you trying to accomplish? Also I'm a bit curious about that, but anyway archive_timeout works even with archive_mode=off. The name looks being a bit off

Re: polygon && polygon and precision

,-0.1))'::polygon; > > select '((3.0e-06,-2),(9.0e-06,-2),(9.0e-06,1),(3.0e-06,1))'::polygon > && > '((2.0e-06,-0.1),(2.0e-06,0.1),(2.01e-06,0.1),(2.01e-06,-0.1))'::polygon; > > Maybe suggests some single-precision floating point use in the > calculations... regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: How to handle CASE statement with PostgreSQL without need for typecasting

s restriction is intended to > prevent surprising conversions from being applied silently. Conversions from the type unkown is not registered in pg_cast. Also CREATE CAST on pseudo types like unknown is not allowed. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Wall shiping replica failed to recover database with error: invalid contrecord length 1956 at FED/38FFE208

Thank you, and sorry for overlooking your comment. At Thu, 14 Nov 2019 12:28:13 -0500, Tom Lane wrote in > Kyotaro Horiguchi writes: > > At Wed, 2 Oct 2019 19:24:02 -0400, Stephen Frost wrote > > in > >> * Tom Lane (t...@sss.pgh.pa.us) wrote: > >>>

Re: How can I pushdown of functions used in targetlist with FDW ?

we don't have that (yet). I'm > unconvinced that ordinary functions ought to be treated as if remote > execution is preferable. Isn't ROUTING MAPPING [1] that? Definers should define one at their own risk as table constraints are. [1] https://www.postgresql.org/message-id/CAD21AoCSzZO%2Bd3E

Re: pg_basebackup

backup. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Wall shiping replica failed to recover database with error: invalid contrecord length 1956 at FED/38FFE208

WAL source. LOG: reached end of WAL during streaming reaplication at 0/A560 on timeline 8 DETAIL: invalid record length at 0/A560: wanted 24, got 0 What do you think about this? regards. -- Kyotaro Horiguchi NTT Open Source Software Center diff --git a/src/backend/access/tran

Re: Create a logical and physical replication

stgresql.org/docs/12/logical-replication.html [2]: https://www.postgresql.org/docs/12/logical-replication-restrictions.html regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Query Tuning

> > -> Result (cost=0.00..0.01 rows=1 width=44) > > CTE approval > > -> Sort (cost=7793.89..7805.22 rows=4530 width=292) regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Referncing a calculated column in a select?

is calculated from t.a. Or CTE (WITH clause) might look better. WITH t1 AS (SELECT a + 3 AS f, b + c AS g FROM t), t2 AS (SELECT f * 3 AS x, f AS y, g + 2 AS z FROM t1) SELECT x, y, z FROM t2; regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: pg full text search very slow for Chinese characters

of characters, which makes it useless. pg_bigm based on bigram/2-gram works better on multibyte characters. https://pgbigm.osdn.jp/index_en.html regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: postmaster utilization

u running? > > How many CPUs on your system? > > What version of Postgres? > > ... What are you using to run the backup? It seems to have been reported as BUG #15961.. https://www.postgresql.org/message-id/15965-413bf5d18aaef...@postgresql.org > PostgreSQL version: 11.4 > Op

Re: question about zeroes in the wal file names

uint32 xrecoff;/* byte offset of location in log file */ } XLogRecPtr; regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Why must AUTOCOMMIT be ON to do txn control in plpgsql procedure?

en on (the default), each SQL command is automatically > committed upon successful completion. To postpone commit in > this mode, you must enter a BEGIN or START TRANSACTION SQL > command. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: terminating walsender process due to replication timeout

rk is having a sort of trouble. Virtual network (local network in a virtual environment) tends to suffer network troubles caused by CPU saturation or something else. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: terminating walsender process due to replication timeout

It is not the same "problem". What was mentioned there is fast network making the sender-side loop busy, which prevents keepalive packet from sending. regards. -- Kyotaro Horiguchi NTT Open Source Software Center

Re: Errors with physical replication

reasonable to > believe that things are working correctly in spite of these errors being > reported. 2) Is there something I should configure differently to avoid > some of these errors? It doesn't seem worth warrying from the viewpoint of data integrity, but if walsender/walreceiver timeout