QUERY: autovacuum: VACUUM ANALYZE table versus QUERY: autovacuum: VACUUM table

Hello list, I am trying to find out if the naming convention from autovacuum does what its command line equivalent does, or at least what I think it does. QUERY: autovacuum: VACUUM ANALYZE table versus autovacuum: VACUUM ANALYZE table. I have been getting my autovacuum tuned and I have the setti

RE: Declarative Range Partitioning Postgres 11

Thanks a ton Michael From: Michael Lewis Sent: November-01-19 3:20 PM To: Shatamjeev Dewan Cc: pgsql-general Subject: Re: Declarative Range Partitioning Postgres 11 On Fri, Nov 1, 2019 at 9:22 AM Shatamjeev Dewan mailto:sde...@nbsps.com>> wrote: Hi Michael, I want to create a partition by ye

RE: Are my autovacuum settings too aggressive for this table?

Michael Lewis writes: >My thinking is opposite from what you have. I consider it important to very >aggressive on autovacuum because it only ever does the required amount of >>work. If a tiny amount of work is needed, it does only that and is done. >Assuming it doesn't cause I/O concerns, do it

Re: Are my autovacuum settings too aggressive for this table?

My thinking is opposite from what you have. I consider it important to very aggressive on autovacuum because it only ever does the required amount of work. If a tiny amount of work is needed, it does only that and is done. Assuming it doesn't cause I/O concerns, do it as often as possible to minimi

Re: Declarative Range Partitioning Postgres 11

On Fri, Nov 1, 2019 at 9:22 AM Shatamjeev Dewan wrote: > Hi Michael, > > > > I want to create a partition by year and subpartition by month in postgres > 11 timestamp column. Please advise syntax. > https://www.postgresql.org/docs/11/ddl-partitioning.html The documentation is rather clear with

Are my autovacuum settings too aggressive for this table?

Hello list, DB1=# select version(); -[ RECORD 1 ] version | PostgreSQL 11.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-23), 64-bit I am sure this question has co

Re: Getting following error in using cursor to fetch the records from a large table in c language(current transaction is aborted, commands ignored until end of transaction block)

On Fri, Nov 1, 2019 at 1:44 PM M Tarkeshwar Rao wrote: > Getting following error in using cursor to fetch the records from a large > table in c language. Regarding this, "c language", I'll comment later > Can you please suggest why it is coming and what is the remedy for this. > Nov 1 13

RE: Declarative Range Partitioning Postgres 11

Hi Michael, I want to create a partition by year and subpartition by month in postgres 11 timestamp column. Please advise syntax. Thanks, Shatamjeev From: Michael Lewis Sent: October-08-19 1:33 PM To: Shatamjeev Dewan Cc: pgsql-general Subject: Re: Declarative Range Partitioning Postgres 11

Getting following error in using cursor to fetch the records from a large table in c language(current transaction is aborted, commands ignored until end of transaction block)

Hi all, Getting following error in using cursor to fetch the records from a large table in c language. Can you please suggest why it is coming and what is the remedy for this. Error Details - Nov 1 13:21:54 sprintstd2 postgres[18604]: [10-1] < 2019-11-01 13:21:54.212 CET

RE: Barman

Thanks Tomas for your inputs. Suppose, if we have database in TB's with OLTP applications then what will be suitable backup strategy. -Original Message- From: Tomas Vondra Sent: Friday, November 1, 2019 12:27 AM To: Daulat Ram Cc: pgsql-general@lists.postgresql.org; pgsql-performa...