Dear all,
I'd like to monitor the resource utilization of logical decoding (e.g.
in version 9.5).
For example, I'd like to see the wal buffer hit ratio, i.e. how much
reading for logical decoding is from in-memory pages.
This can be set by blks_hit/(blks_read+blks_hit) from pg_stat_database.
Hi,
I intend to increase the speed of streaming replication with logical
decoding using following configuration:
wal_level = logical
fsync = on
synchronous_commit = off
wal_sync_method = fdatasync
wal_buffers = 256MB
wal_writer_delay = 2seconds
checkpoint_timeout = 15min
max_wal_size=10GB
based change data capture.
Weiping
On 27.10.2017 14:03, Francisco Olarte wrote:
On Fri, Oct 27, 2017 at 12:04 PM, Weiping Qu <q...@informatik.uni-kl.de> wrote:
That's a good point and we haven't accounted for disk caching.
Is there any way to confirm this fact in PostgreSQL?
I doubt, as it
That's a good point and we haven't accounted for disk caching.
Is there any way to confirm this fact in PostgreSQL?
Weiping
On 27.10.2017 11:53, Francisco Olarte wrote:
On Thu, Oct 26, 2017 at 10:20 PM, Weiping Qu <q...@informatik.uni-kl.de> wrote:
However, the plots showed different
could get your partition full of xlog.
Regards,
Alvaro Aguayo
Operations Manager
Open Comb Systems E.I.R.L.
Office: (+51-1) 3377813 | Mobile: (+51) 995540103 | (+51) 954183248
Web: www.ocs.pe
- Original Message -
From: "Weiping Qu" <q...@informatik.uni-kl.de>
To: "
Dear postgresql community,
I have a question regarding understanding the implementation logic
behind logical replication.
Assume a replication slot created on the master node, will more and more
data get piled up in the slot and the size of replication slot
continuously increase if there is
that it is a bug. Thank you for report. I guess it will be
fixed soon.
On 01.03.2016 17:36, Weiping Qu wrote:
Dear postgresql general mailing list,
I am currently using the logical decoding feature (version 9.6 I think
as far as I found in the source, wal_level: logical,
max_replication_slot: >
Dear postgresql general mailing list,
I am currently using the logical decoding feature (version 9.6 I think
as far as I found in the source, wal_level: logical,
max_replication_slot: > 1, track_commit_timestamp: on, I am not sure
whether this will help or not).
Following the online
Dear postgresql general mailing list,
I am currently using the logical decoding feature (version 9.6 I think
as far as I found in the source, wal_level: logical,
max_replication_slot: > 1, track_commit_timestamp: on, I am not sure
whether this will help or not).
Following the online
If you received this message twice, sorry for annoying since I did not
subscribe successfully previously due to conflicting email domain.
Dear postgresql general mailing list,
I am currently using the logical decoding feature (version 9.6 I think
as far as I found in the source, wal_level:
10 matches
Mail list logo
