Thanks for the suggestions.
On Fri, May 14, 2010 at 1:28 PM, Bruce Momjian wrote:
> Anj Adu wrote:
>> Will any upcoming release of Postgres have an incremental backup tool
>> like Oracle's RMAN? Currently, the WAL based archiving requires many
>> frequent full backups (especially for large datab
Anj Adu wrote:
> Will any upcoming release of Postgres have an incremental backup tool
> like Oracle's RMAN? Currently, the WAL based archiving requires many
> frequent full backups (especially for large databases) as the replay
> of a large number of WAL files will take a very long time. We have
Anj Adu wrote:
> Will any upcoming release of Postgres have an incremental backup
> tool like Oracle's RMAN? Currently, the WAL based archiving
> requires many frequent full backups (especially for large
> databases) as the replay of a large number of WAL files will take
> a very long time. We
On Fri, 2010-05-14 at 13:12 -0700, Anj Adu wrote:
> Will any upcoming release of Postgres have an incremental backup tool
> like Oracle's RMAN? Currently, the WAL based archiving requires many
> frequent full backups (especially for large databases) as the replay
> of a large number of WAL files w
Will any upcoming release of Postgres have an incremental backup tool
like Oracle's RMAN? Currently, the WAL based archiving requires many
frequent full backups (especially for large databases) as the replay
of a large number of WAL files will take a very long time. We have a
few databases each ov
Yes, the query planner is part of Postgres itself. Here are some pages
of the manual that talk about the planner and how it works:
http://www.postgresql.org/docs/8.3/static/using-explain.html
http://www.postgresql.org/docs/8.3/static/planner-stats.html
And this talks about configuration option
Hi Lewis,
Thanks for the clarification.
Referring to the statement in postgresql-8.2-US.pdf document "ANALYZE
collects statistics about the contents of tables in the database ...
query planner uses these statistics to help determine the most efficient
execution plans for queries."
From your resp
"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
You misunderstand the purpose of ANALYZE. Postgres needs the results in
order to perform queries efficiently. Whether you have the ability to
change or tune the queries is beside the point.
- Lewis
On 5/14/2010 11:01 AM, Narasimha Murthy-VRFX87 wrote:
Hi Kevin,
Thanks again for a quick re
Hi Kevin,
Thanks again for a quick response.
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
"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
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
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 and ANALYZE. I do not see any option to disable running ANALYZE
during auto-vacu
"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
Hi Guillaume,
Thanks for a quick response.
How do I check this? Please clarify.
Regards, Narasimha Murthy
Cell +91 95814 98895, +91-94940 62794 | 040-2347 2025 (O) | x2025 (O)
-Original Message-
From: Guillaume Lelarge [mailto:guilla...@lelarge.info]
Sent: Friday, May 14, 2010 6:34 PM
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
>
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
On Fri, May 14, 2010 at 1:55 AM, Vinay Sarvana wrote:
> Hi. Is there any possibility for creating trigger file automatically in
> postgres. Scenario is as follows :
>
> There are some application which is having this postgres database. There
> are main & backup database. Application is normally co
18 matches
Mail list logo
