RE: Getting following error in using cursor to fetch the records from a large table in c language

2019-10-31 Thread M Tarkeshwar Rao
When we running with vacuum full we are getting following error message. Error: --- user was holding a relation lock for too long Any idea about this error. -Original Message- From: Laurenz Albe Sent: Thursday, October 31, 2019 12:28 PM To: M Tarkeshwar Rao ; 'pgsql-gene...@postgr

Re: Can you please suggest how to configure hot_standby_feedback?

2019-10-31 Thread Andreas Kretschmer
Am 31.10.19 um 06:21 schrieb M Tarkeshwar Rao: Can you please suggest how to configure hot_standby_feedback? turn it on if you want execute long running queries on the standby, keep in mind it can lead to more bloat on the master. Regards, Andreas -- 2ndQuadrant - The PostgreSQL Supp

Re: Automatically parsing in-line composite types

2019-10-31 Thread Merlin Moncure
On Wed, Oct 30, 2019 at 5:41 PM Andres Freund wrote: > > Hi, > > On 2019-10-29 14:33:00 -0400, Tom Lane wrote: > > Mitar writes: > > > I think RowDescription should be extended to provide full recursive > > > metadata about all data types. That would be the best way to do it. > > > > [ shrug... ]

Re: Automatically parsing in-line composite types

2019-10-31 Thread Tom Lane
Merlin Moncure writes: > On Wed, Oct 30, 2019 at 5:41 PM Andres Freund wrote: >> Hm. Wouldn't it be fairly easy to allow the client to specify how much >> metadata they'd want? I.e. opt-in into getting more complete metadata? > Suppose you had a set of 1000 records, with an array of composites (

Re: Automatically parsing in-line composite types

2019-10-31 Thread Mitar
Hi! On Thu, Oct 31, 2019 at 7:59 AM Tom Lane wrote: > tl;dr: there are a lot more worms in this can than you might guess. But with all those issues, how do people then use compound types in practice at all? Just at the top-level and have custom code to parse them out for every query they are mak

Barman

2019-10-31 Thread Daulat Ram
Hi All, We have configured postgres 11.2 in streaming replication (primary & Standby) on docker and I am looking to initiate the Postgres backup using barman. As I know there are few options for taking backup using barman. RSYNC backup Incremental Backups Streaming Backup with continuous WAL s

Re: Barman

2019-10-31 Thread Tomas Vondra
On Thu, Oct 31, 2019 at 05:29:34PM +, Daulat Ram wrote: Hi All, We have configured postgres 11.2 in streaming replication (primary & Standby) on docker and I am looking to initiate the Postgres backup using barman. As I know there are few options for taking backup using barman. RSYNC backu

Re: Getting following error in using cursor to fetch the records from a large table in c language

2019-10-31 Thread Laurenz Albe
M Tarkeshwar Rao wrote: > When we running with vacuum full we are getting following error message. > > Error: > --- > user was holding a relation lock for too long > > Any idea about this error. That means that you got a replication conflict, which is to be expected, because VACUUM (FULL) is

logging proxy

2019-10-31 Thread Олег Самойлов
Does anyone know PostgresQL proxy which can log queries with username, ip and affected rows for security reason. PostgresQL itself can log almost all, except affected rows.

RE: Getting following error in using cursor to fetch the records from a large table in c language

2019-10-31 Thread M Tarkeshwar Rao
Hi, If VACUUM full is going on and any conflicting query come then what will happen to that query. Regards Tarkeshwar -Original Message- From: M Tarkeshwar Rao Sent: Thursday, October 31, 2019 12:45 PM To: Laurenz Albe ; 'pgsql-gene...@postgresql.org' Subject: RE: Getting following e