ml ml wrote:
> i am using the following archive command:
>archive_command = '/usr/bin/rsync -a -F /data/pgsql/%p
> pg...@pg-backup:/restore/walfiles/'
>
> Which works perfectly so far. My problem now is, what happens if the
> "pg-backup" server is down for some time and the archove command
Dear Gurus,
I need some solution for a transaction-based system that may have
offline clients. Something like CVS in version management, but
SQL-based.
I need this because we have a team of 6 people, concurrently updating
shared XML files and such. When I leave the corporate network I can
keep up
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> - Way of handling conflicting records
> e.g. client A goes offline, client B modifies master, client A
> modifies locally, and when goes online again cann
Hello again.
I have an update, hoping someone can steer me in the right direction here.
After receiving the "could not access transaction" error mentioned in my
previous email I did some more digging and found that people have had
success resolving this issue using pg_resetxlog.
I gave this a tr
Hi
Some one know why this is happening?
I change the OS to 64 bits and now the oom-killer not hapend but Postgres is
still showing out of memory
Linux SERVER 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64
x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5.2 (Tikang
On Fri, Jul 31, 2009 at 8:01 PM, Michael Clark wrote:
> I tried this, and might have exposed another issue.
> Now I am getting:
> ERROR: could not access status of transaction 3839923882
> DETAIL: could not open file "pg_clog/0E4E": No such file or directory.
> I checked the pg_clog folder, and the
Hello,
Thanks for the reply.
On Fri, Jul 31, 2009 at 5:24 PM, Greg Stark wrote:
> > I tried this, and might have exposed another issue.
> > Now I am getting:
> > ERROR: could not access status of transaction 3839923882
> > DETAIL: could not open file "pg_clog/0E4E": No such file or directory.
>
Michael Clark writes:
> On Fri, Jul 31, 2009 at 5:24 PM, Greg Stark wrote:
>>> Now I am getting:
>>> ERROR: could not access status of transaction 3839923882
>> How long has this database been in use? That's a very high transaction
>> number that would only be reached on a heavily used database
I believe you may be right - need to do some more testing.
Apparently the error which I saw in the log was generated while
debugging the stored procedure using SQL Studio for PostgreSQL. I guess
it has its own interpreter for plpgsql and must be typecasting while
executing each row.
We can consid
