Re: [GENERAL] Postgresql 9.2 has standby server lost data?

On 06/19/2015 01:05 PM, Paula Price wrote: On Fri, Jun 19, 2015 at 12:01 PM, Adrian Klaver mailto:adrian.kla...@aklaver.com>> wrote: On 06/18/2015 05:45 PM, Paula Price wrote: I have Postgresql 9.2.10 streaming replication set up with log shipping in case the repli

Re: [GENERAL] Is there any way to measure disk activity for each query?

Le 19/06/2015 01:07, Jeff Janes a écrit : > On Thu, Jun 18, 2015 at 3:05 PM, Oleg Serov > wrote: > > Hello! > > I'm wondering, if there any way to measure how much disk-io were > generated by a query? > > > For an individual query execution, you can explai

Re: [GENERAL] Postgres SIGALRM timer

Scottix writes: > I am running a posgres server with a zabbix server and zabbix agent and I > am getting a bunch errors about SIGALRM, It makes postgres drop connections > randomly. > 2015-06-19 08:45:22 PDT FATAL: could not enable SIGALRM timer: Invalid > argument That's really weird. [ looks

Re: [GENERAL] pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux

Douglas Stetner writes: > On 18 Jun 2015, at 02:06 , Tom Lane wrote: >> Douglas Stetner writes: >>> Looking for confirmation there is an issue with pg_dump failing after >>> upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux. >> Quick thought --- did you restart the Postgres service

Re: [GENERAL] Postgresql 9.2 has standby server lost data?

On 06/18/2015 05:45 PM, Paula Price wrote: I have Postgresql 9.2.10 streaming replication set up with log shipping in case the replication falls behind. I discovered that the log-shipping had been disabled at some point in time. I enabled the log shipping again. If at some point in time the st

[GENERAL] Postgres SIGALRM timer

I am running a posgres server with a zabbix server and zabbix agent and I am getting a bunch errors about SIGALRM, It makes postgres drop connections randomly. Ubuntu 14.04.2 LTS Linux Host 3.19.0-21-generic #21~14.04.1-Ubuntu SMP Sun Jun 14 18:45:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Postgre

[GENERAL] Postgresql 9.2 has standby server lost data?

I have Postgresql 9.2.10 streaming replication set up with log shipping in case the replication falls behind. I discovered that the log-shipping had been disabled at some point in time. I enabled the log shipping again. If at some point in time the streaming replication fell behind and the stand

Re: [GENERAL] pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux

> > On 18 Jun 2015, at 02:06 , Tom Lane wrote: > > Douglas Stetner writes: >> Looking for confirmation there is an issue with pg_dump failing after >> upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux. > > Quick thought --- did you restart the Postgres service after upgrading > ope

[GENERAL] Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux

Tom Lane wrote: > Douglas Stetner writes: >> Looking for confirmation there is an issue with pg_dump failing after >> upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux. > > Quick thought --- did you restart the Postgres service after upgrading > openssl? If not, your server is still u

Re: [GENERAL] How to craft a query that uses memory?

Note that after cranking up work mem you then need a query that can use it. Quickest way to use LOTS of memory is to do a lot of unconstrained joins. select * from table a join table b on (true) join table c on (true) join table d on (true); Result set is size of a*b*c*d On Fri, Jun 19, 2015 at 7

Re: [GENERAL] Planner cost adjustments

Here is a last follow-up on adjusting the planner costs calculation 1 - Francisco, you provide me with a clue I was looking for at this point! I learned enough PLpgsql over the last week to reprogram all my processes (not always elegant but it works). By processing individual records using loop

Re: [GENERAL] Transaction abort difference between psql, isql, ODBC and JDBC pgsql 8.4

On 06/19/2015 04:15 AM, Gary Cowell wrote: Hello I'm aware of the automatic transaction abort that occurs in PostgreSQL if you have DML throw an error during a transaction, this prevents future selects within transaction, until rollback or commit (and hence, new transaction). I'm okay with this.

Re: [GENERAL] How to craft a query that uses memory?

Albe Laurenz wrote on Friday, June 19, 2015 12:56 PM: > Holger Friedrich wrote: > > So how do I craft a query that actually does use lots of memory? > You increase the parameter "work_mem". > You can do that globally in postgresql.conf or with SET for one session or > with SET LOCAL for one tran

Re: [GENERAL] Transaction abort difference between psql, isql, ODBC and JDBC pgsql 8.4

> From: Gary Cowell >To: pgsql-general@postgresql.org >Sent: Friday, 19 June 2015, 12:15 >Subject: [GENERAL] Transaction abort difference between psql, isql, ODBC and >JDBC pgsql 8.4 > > > >Hello > >I'm aware of the automatic transaction abort that occurs in PostgreSQL if you >have DML throw

[GENERAL] Transaction abort difference between psql, isql, ODBC and JDBC pgsql 8.4

Hello I'm aware of the automatic transaction abort that occurs in PostgreSQL if you have DML throw an error during a transaction, this prevents future selects within transaction, until rollback or commit (and hence, new transaction). I'm okay with this. Doing all this on Red Hat 6.5 with Postgres

Re: [GENERAL] How to craft a query that uses memory?

Holger Friedrich wrote: > So how do I craft a query that actually does use lots of memory? You increase the parameter "work_mem". You can do that globally in postgresql.conf or with SET for one session or with SET LOCAL for one transaction. Yours, Laurenz Albe -- Sent via pgsql-general mailing

[GENERAL] How to craft a query that uses memory?

Hello list, What would be the best way of setting up a query that uses lots of memory, in order to study the effects of resource usage parameters on the performance of the query? I thought that a query on a large table involving JOINs would be a way, but while the backend initially used 1.7 gi

Re: [GENERAL] valgrind

Peter Kroon wrote: > ==3814== Memcheck, a memory error detector > ==3814== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > ==3814== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info > ==3814== Command: ./pgsql_check > ==3814== > ==3814== > ==3814== HEAP SUMMARY: >