RE: database crash during pgbench run

2018-12-11 Thread Greg Clough
> > 2018-12-10 19:11:56 IST  23647  LOG:  received fast shutdown request
> > any idea what can cause it ?
>
>Something sent SIGINT to the postmaster.

My money is on the OoM (Out of Memory) killer.  The standard PDGD install on 
CentOS should disable that, but I'm not sure what OS you're on or how 
PostgreSQL was installed.

Greg Clough.










This e-mail, including accompanying communications and attachments, is strictly 
confidential and only for the intended recipient. Any retention, use or 
disclosure not expressly authorised by IHSMarkit is prohibited. This email is 
subject to all waivers and other terms at the following link: 
https://ihsmarkit.com/Legal/EmailDisclaimer.html

Please visit www.ihsmarkit.com/about/contact-us.html for contact information on 
our offices worldwide.



RE: pgbench results arent accurate

2018-12-14 Thread Greg Clough
> I installed a new postgres 9.6 on both of my machines.

Where is your storage?  Is it local, or on a SAN?  A SAN will definitely have a 
cache, so possibly there is another layer of cache that you’re not accounting 
for.

Greg Clough.



This e-mail, including accompanying communications and attachments, is strictly 
confidential and only for the intended recipient. Any retention, use or 
disclosure not expressly authorised by IHSMarkit is prohibited. This email is 
subject to all waivers and other terms at the following link: 
https://ihsmarkit.com/Legal/EmailDisclaimer.html

Please visit www.ihsmarkit.com/about/contact-us.html for contact information on 
our offices worldwide.


RE: upgrade to PG11 on secondary fails (no initdb was launched)

2019-05-23 Thread Greg Clough
> 2019-05-23 04:17:02 EDT  23593  DETAIL:  The database cluster was initialized 
> with PG_CONTROL_VERSION 960, but the server was compiled with 
> PG_CONTROL_VERSION 1100.

It appears that you have not upgraded the standby server, so either use "rsync" 
or simply destroy and rebuild it from scratch "repmgr standby clone..."

  https://www.postgresql.org/docs/11/pgupgrade.html

  Upgrade Streaming Replication and Log-Shipping standby servers

  If you used link mode and have Streaming Replication (see Section 26.2.5) 
or Log-Shipping (see Section 26.2) standby servers, you can follow these steps 
to quickly upgrade them. You will not be running pg_upgrade on the standby 
servers, but rather rsync on the primary. Do not start any servers yet.

  If you did not use link mode, do not have or do not want to use rsync, or 
want an easier solution, skip the instructions in this section and simply 
recreate the standby servers once pg_upgrade completes and the new primary is 
running.

Greg.







This e-mail, including accompanying communications and attachments, is strictly 
confidential and only for the intended recipient. Any retention, use or 
disclosure not expressly authorised by IHSMarkit is prohibited. This email is 
subject to all waivers and other terms at the following link: 
https://ihsmarkit.com/Legal/EmailDisclaimer.html

Please visit www.ihsmarkit.com/about/contact-us.html for contact information on 
our offices worldwide.