Re: [ADMIN] Clarification when using Continous Archiving in 8.4

On Fri, Aug 9, 2013 at 10:20:13AM +0200, Jan Lentfer wrote: > On Thu, 8 Aug 2013 21:36:35 -0400, Bruce Momjian wrote: > > On Tue, Jul 16, 2013 at 11:30:54AM -0500, Nestor A. Diaz wrote: > > Hello People, In reference to my last post , my question is: It is > possible to recov

Re: [ADMIN] Clarification when using Continous Archiving in 8.4

On Thu, 8 Aug 2013 21:36:35 -0400, Bruce Momjian wrote: > On Tue, Jul 16, 2013 at 11:30:54AM -0500, Nestor A. Diaz wrote: > >> Hello People, In reference to my last post , my question is: It is possible to recover more (subsequent) WAL files when I have already recover a postgres 8.4 databas

Re: [ADMIN] Clarification when using Continous Archiving in 8.4

On Tue, Jul 16, 2013 at 11:30:54AM -0500, Nestor A. Diaz wrote: > Hello People, > > In reference to my last post , my question is: It is possible to recover more > (subsequent) WAL files when I have already recover a postgres 8.4 database > using a PITR ? I have read on some places that it's not p

[ADMIN] Clarification when using Continous Archiving in 8.4

Hello People, In reference to my last post , my question is: It is possible to recover more (subsequent) WAL files when I have already recover a postgres 8.4 database using a PITR ? I have read on some places that it's not pos

Re: [ADMIN] Clarification on start/stop backup

Scott Whitney wrote: > I'll be moving to PG9 (hopefully soon...probably 6 weeks). > > At that time, I'll be setting up hot-standby with streaming replication to 2 > sites. Off-siting my > pgdumps nightly is no longer going to be possible in the very near future, > due to the size of the > dumps.

[ADMIN] Clarification on start/stop backup

I'll be moving to PG9 (hopefully soon...probably 6 weeks). At that time, I'll be setting up hot-standby with streaming replication to 2 sites. Off-siting my pgdumps nightly is no longer going to be possible in the very near future, due to the size of the dumps. So...what I had planned to do wa

Re: [ADMIN] Clarification of pg_cotroldata output

Melvin Davidson wrote: > When I execute pg_control on a warm standby cluster, I notice that > often, "Time of latest checkpoint:" lags behind "pg_control last > modified:". > > Is it documented anywhere the difference between "pg_control last > modified:" and "Time of latest checkpoint:" ? If

[ADMIN] Clarification of pg_cotroldata output

*Can someone please clarify? When I execute pg_control on a warm standby cluster, I notice that often, "Time of latest checkpoint:" lags behind "pg_control last modified:". Is it documented anywhere the difference between "pg_control last modified:" and "Time of latest checkpoint:" ? Thanks in

Re: [ADMIN] Clarification Needed: When does autovacuum daemon run?

Excerpts from Narasimha Murthy-VRFX87's message of jue may 20 02:47:21 -0400 2010: > Hi Alvaro Herrera, > > Since, my original plan was to run the auto-vacuum daily EXACTLY at 5 am, I > wanted to know which seconds of a minute. My query in other word was, if I > set autovacuum_naptime to 1 hr,

Re: [ADMIN] Clarification Needed: When does autovacuum daemon run?

lto:pgsql-admin-ow...@postgresql.org] On Behalf Of Alvaro Herrera Sent: Thursday, May 20, 2010 2:21 AM To: Narasimha Murthy-VRFX87 Cc: Ian Lea; Devrim GÜNDÜZ; pgsql-admin Subject: Re: [ADMIN] Clarification Needed: When does autovacuum daemon run? Excerpts from Narasimha Murthy-VRFX87's message of ma

Re: [ADMIN] Clarification Needed: When does autovacuum daemon run?

Excerpts from Narasimha Murthy-VRFX87's message of mar may 18 07:04:34 -0400 2010: > I need some more clarification. autovacuum_naptime takes one minute by > default. In this case, which second of each minute the autovacuum > daemon runs (provided it is enabled)? Why does it matter which second

Re: [ADMIN] Clarification Needed: When does autovacuum daemon run?

Excerpts from Narasimha Murthy-VRFX87's message of mar may 18 05:56:26 -0400 2010: > Hello, > > Postgresql-8.2 manual has mentioned following points. > * The autovacuum daemon, when enabled, runs every autovacuum_naptime > seconds. > * autovacuum_naptime (integer): Specifies the delay between "a

Re: [ADMIN] Clarification Needed: When does autovacuum daemon run?

? Regards, Narasimha Murthy Cell +91 95814 98895, +91-94940 62794 | 040-2347 2025 (O) | x2025 (O) -Original Message- From: Ian Lea [mailto:ian@gmail.com] Sent: Tuesday, May 18, 2010 3:43 PM To: Narasimha Murthy-VRFX87 Subject: Re: [ADMIN] Clarification Needed: When does autovacuum daemon run?

Re: [ADMIN] Clarification Needed: When does autovacuum daemon run?

On Tue, 2010-05-18 at 17:56 +0800, Narasimha Murthy-VRFX87 wrote: > My Query: I want to run autovacuum daemon everyday at 5 am. That is not "auto"vacuum. What you want is manual vacuum. -- Devrim GÜNDÜZ PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer PostgreSQL RPM Repository: http:/

[ADMIN] Clarification Needed: When does autovacuum daemon run?

Hello, Postgresql-8.2 manual has mentioned following points. * The autovacuum daemon, when enabled, runs every autovacuum_naptime seconds. * autovacuum_naptime (integer): Specifies the delay between "activity rounds" for the autovacuum daemonThe delay is measured in seconds, and the default i

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

arasimha Murthy Cell +91 95814 98895, +91-94940 62794 | 040-2347 2025 (O) | x2025 (O) -Original Message- From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Lewis Kapell Sent: Friday, May 14, 2010 8:34 PM To: pgsql-admin@postgresql.org Subject: Re: [

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

] On Behalf Of Lewis Kapell Sent: Friday, May 14, 2010 8:34 PM To: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode You misunderstand the purpose of ANALYZE. Postgres needs the results in order to perform queries efficiently. Whether you have t

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

"Narasimha Murthy-VRFX87" wrote: > I am using a 3rd party application, which in turn using PostgreSQL > DB. I can not change/tune the SQL queries, performed by the 3rd > party application. Hence, the statistics generated by ANALYZE, is of no > use to me. That is the reason, I have planned not to

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

Murthy Cell +91 95814 98895, +91-94940 62794 | 040-2347 2025 (O) | x2025 (O) -Original Message- From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov] Sent: Friday, May 14, 2010 8:18 PM To: Narasimha Murthy-VRFX87 Cc: pgsql-admin@postgresql.org Subject: RE: [ADMIN] Clarification required

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

Subject: RE: [ADMIN] Clarification required: autovacuum and VACUUM command mode "Narasimha Murthy-VRFX87" wrote: > Another query: I do not want to run Analyze. However, auto-vacuum runs > both both VACUUM and ANALYZE. I do not see any option to disable > running ANALYZE dur

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

"Narasimha Murthy-VRFX87" wrote: > Another query: I do not want to run Analyze. However, auto-vacuum > runs both both VACUUM and ANALYZE. I do not see any option to > disable running ANALYZE during auto-vacuum. Is there any way to > achive this? Usually it's best to run ANALYZE more often than

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

On Fri, May 14, 2010 at 8:20 AM, Narasimha Murthy-VRFX87 wrote: > Hi Kevin, > > Thanks for the clarification. > > I have planned to schedule Lazy Vacuum (, not FULL Vacuum) using auto-vacuum > daemon. > > Another query: I do not want to run Analyze. However, auto-vacuum runs both > both VACUUM a

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode "Narasimha Murthy-VRFX87" wrote: > Guillaume Lelarge wrote: >> Le 14/05/2010 14:52, Narasimha Murthy-VRFX87 a écrit : >>> VACUUM command works either in plai

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

"Narasimha Murthy-VRFX87" wrote: > Guillaume Lelarge wrote: >> Le 14/05/2010 14:52, Narasimha Murthy-VRFX87 a écrit : >>> VACUUM command works either in plain mode (if we do not specify >>> FULL) or in FULL mode. When autovacuum is enabled, what mode >>> does it run the VACUUM command (in plain

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

To: Narasimha Murthy-VRFX87 Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode Hi, Le 14/05/2010 14:52, Narasimha Murthy-VRFX87 a écrit : > [...] > I need a clarification on auto-vacuum. Appreciate any > clarification/help.

Re: [ADMIN] Clarification required: autovacuum and VACUUM command mode

Hi, Le 14/05/2010 14:52, Narasimha Murthy-VRFX87 a écrit : > [...] > I need a clarification on auto-vacuum. Appreciate any > clarification/help. > > As explained in page 1093 of postgresql-8.2-US.pdf, VACUUM command works > either in plain mode (if we do not specify FULL) or in FULL mode. When >

[ADMIN] Clarification required: autovacuum and VACUUM command mode

Hello, I need a clarification on auto-vacuum. Appreciate any clarification/help. As explained in page 1093 of postgresql-8.2-US.pdf, VACUUM command works either in plain mode (if we do not specify FULL) or in FULL mode. When autovacuum is enabled, what mode does it run the VACUUM command (in pl

[ADMIN] clarification

In my previous post, > I intentionally used the same user name for both versions, only used a > different directory. The two installations share the same PGDATA > environment variable. I want to clarify the above. I wanted to say "Although I have two versions of postgres, because I have only one