From: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: hot spare / log shipping work on |
Date: | 2004-08-13 22:49:28 |
Message-ID: | 411D4578.6040206@bigfoot.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Gaetano Mendola <mendola(at)bigfoot(dot)com> writes:
>
>>I'm facing however to the following problems:
>
>
>>1) Discovery the actual WAL file
>> I'm supposing is the last modified file inside the
>> pg_xlog directory. If this is not the good method
>> may I know how I can know it ?
>
>
> While that theoretically will work, it leaves a bad taste in my mouth.
> I have been thinking of proposing that we add a "pg_current_wal_file()"
> function, or some such name, to return the name of the active WAL file.
Totally agree, this could help during the process.
Actually I detect the current wal file in this way:
ls -t1p $PGXLOGDIR | grep -v / | head 1
that is an almost "empirical" process, in the first phase
I can live with it but for sure a more robust way is a must.
Regards
Gaetano Mendola
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2004-08-13 22:54:08 | Re: Postgres 8.0 -> BEGIN EXCEPTION END Syntax???? |
Previous Message | Jim C. Nasby | 2004-08-13 22:49:07 | Re: Calling PL functions with named parameters |