We need PITR, but our legacy application can't be upgraded to 7.4 Postgresql version
because of autocommit handling change. So I'll try to follow Simon development of PITR
for 7.5 PITR and backport it to 7.3.
Why not use replication instead?
Best regards
--
Command Prompt, Inc., home of
Hi, tom
> > I tried to backport Simon Riggs patches for 7.4.x series to 7.3.x
> > with addition of python implementation of pg_arch.
>
> > It can be of interest if you consider to continue using 7.3 series of
> > postgresql.
>
> Surely you jest.
>
Nope. We have a reason for it.
> You are going
"=?koi8-r?b?8M/UxdLRxdc=?= =?koi8-r?b?IOku5S4=?=" <[EMAIL PROTECTED]> writes:
> I tried to backport Simon Riggs patches for 7.4.x series to 7.3.x
> with addition of python implementation of pg_arch.
> It can be of interest if you consider to continue using 7.3 series of
> postgresql.
Surely you j
Hi,
I tried to backport Simon Riggs patches for 7.4.x series to 7.3.x
with addition of python implementation of pg_arch.
It can be of interest if you consider to continue using 7.3 series of postgresql.
src/backend/access/transam/xlog.c: calls to "ereport" was replaced with call to
"elog".
src
