Mikel Lindsaar wrote:
linkd d:\PostgreSQL\8.3\data\pg_xlog "C:\Program
Files\PostgreSQL\transaction_log\pg_xlog"
The correct xlog path is $PGDATA\pg_xlog. Normally, it is 'C:\Program
Files\PostgreSQL\X.X\data\pg_xlog'.
--
Euler Taveira de Oliveira
ht
"Orion Henry" <[EMAIL PROTECTED]> writes:
> 2008-04-13 12:26:48 PDT LOG: background writer process (PID 965) was
> terminated by signal 9
Turn off memory overcommit.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to you
Hello. I need help tracking down a crash bug. I'm running 8.2.7
I've had my database go into recovery mode three times so far today under
user load. /etc/init.d/postgresql-8.2 stop would stop the backend but leave
a few processes behind like this
postgres 22318 0.0 0.0 45724 1272 ?S
Hello. I need help tracking down a crash bug. I'm running 8.2.7
I've had my database go into recovery mode three times so far today under
user load. /etc/init.d/postgresql-8.2 stop would stop the backend but leave
a few processes behind like this
postgres 22318 0.0 0.0 45724 1272 ?S
Magnus Hagander wrote:
In general, mingw built modules should load just fine in msvc built
postgres. AFAIK, that's how PostGIS does it for 8.3 (though I know Mark
is working on getting MSVC build support for them). Debugging may be a
bit harder (since they use different kinds of debug symbols - p
Hello Tom,
it seems that i can't reproduce it too at the moment. When i see the bug
again i will directly send you the data, but it must be something like that:
INSERT INTO benutzer (pnr, vorname, nachname, nutzerkennung, passwort,
plz, ort, strasse, hausnummer, telefon_dienst, telefon_privat
Thanks for the clarification, Dave. I posted the question here because this
was the only place I could find where there already seemed to be a relevant
discussion, but now I know about the EDB forum that's obviously a much
better place.
In terms of the problem, I downloaded the EDB AS 8.3 instal
