On Wed, 2007-01-17 at 23:03 +0500, Shoaib Mir wrote:
archive_timeout (came in ver 8.2) might help you with customizing the
size for log files.
I'm not sure that it will.
If anything it could produce more log files, which could lead to a
backlog if the archive_command isn't functioning for some
Suggested in case he wants to do a log switch after certain amount of
time...
---
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/18/07, Simon Riggs [EMAIL PROTECTED] wrote:
On Wed, 2007-01-17 at 23:03 +0500, Shoaib Mir wrote:
archive_timeout (came in ver 8.2) might help you with
Hi,
how can I monitor the size of the transaction log files using SQL Statements?
Best Regards
Silvio
Silvio Ziegelwanger
Research Development
Fabalabs Software GmbH
Honauerstraße 4
4020 Linz
Austria
Tel: [43] (732) 60 61 62
Fax: [43] (732) 60 61 62-609
E-Mail: [EMAIL PROTECTED]
Ziegelwanger, Silvio wrote:
Hi,
how can I monitor the size of the transaction log files using SQL Statements?
You can't. You would have to write a custom function to heck the size of
the xlog directory.
Sincerely,
Joshua D. Drake
Best Regards
Silvio
Silvio
archive_timeout (came in ver 8.2) might help you with customizing the size
for log files.
-
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/17/07, Joshua D. Drake [EMAIL PROTECTED] wrote:
Ziegelwanger, Silvio wrote:
Hi,
how can I monitor the size of the transaction
Joshua D. Drake wrote:
Ziegelwanger, Silvio wrote:
Hi,
how can I monitor the size of the transaction log files using SQL Statements?
You can't. You would have to write a custom function to heck the size of
the xlog directory.
wel in recent versions of pg it should be pretty easy to do
Joshua D. Drake [EMAIL PROTECTED] writes:
Ziegelwanger, Silvio wrote:
how can I monitor the size of the transaction log files using SQL Statements?
You can't. You would have to write a custom function to heck the size of
the xlog directory.
Perhaps more to the point, why do you think you
