hello, at most 40% total memory, official doc also says so.you can testify it
using pg_prewarm and pgfincore .
btw, numa supported? if so, extra care is necessary when starting db cluster.
從我的 Samsung Galaxy 智慧型手機傳送。
原始訊息 自： Bill Moran 日期： 2017/5/24
20:24 (GMT+08:00) 至： pgsq
ernet
for postgre share buffer issue. you will find what you want.
steven
從我的 Samsung Galaxy 智慧型手機傳送。
原始訊息 自： Bill Moran 日期： 2017/5/24
22:52 (GMT+08:00) 至： stevenchang1213 副本：
pgsql-general@postgresql.org 主旨： Re: [GENERAL] Current best practice for
maximum shared_buffers s
for ur reference
https://madusudanan.com/blog/understanding-postgres-caching-in-depth/
從我的 Samsung Galaxy 智慧型手機傳送。
原始訊息 自： stevenchang1213 日期：
2017/5/24 23:48 (GMT+08:00) 至： Bill Moran 副本：
pgsql-general@postgresql.org 主旨： Re: [GENERAL] Current best practice for
maximum
tell me where this function add_job_history() is?Actually, I don't think you
can count on ora2pg to transform your pl/sql code to plpgsql or other
(un)trusted procedural language code. It's not that simple!you can type "\df
add_job_history" in psql session to check it's existence if it belon
this chapter introduces mvcc
http://www.interdb.jp/pg/pgsql05.html
原始訊息 自： rajan 日期： 2017/7/1 14:32
(GMT+08:00) 至： pgsql-general@postgresql.org 主旨： [GENERAL] have trouble
understanding xmin and xmax with update operations from two different sessions
have trouble understandi
I just finished a point in time recovery from a rsync physical data file
backup + wal archive.Of course it works!You can also achieve the same goal
through pg_basebackup.
By your descriptions, your vendor seems to use logical backup through pg_dump.
Anyway you can only achieve no data loss thro
