Hi!
I found a strange hunging of postgres 6.5.
In a few days working child process dumped to core but postmaster was runned it
looks like
16890 p5 S0:00 (postmaster)
i.e. daed and lying in swap.
After ~8 such daed parent postmaster becomes refusing connections...
I tried to simulate this s
Hello,
I installed PostgreSQL 6.4.2 and had it running without any problem for
several months, it even passed the regression tests almost perfectly
(!!! a first time for me)... After 6.5 came out, I completely removed
the 6.4.2 installation with a `rm -r /usr/local/pgsql/` soon followed by
a `sh
This appears to be fixed in 6.5.
> On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
>
> > If your query is bigger than 8192 bytes then libpq simply truncates it
> > without giving any warning
>
> I've read that in the docs, too (while back, didn't try it out). I have
> to say, t
> I had two identical postgres users in my pg_users table. (Why does that
> keep occurring? I also had to versions of each table I made.)
I would love to know how that happens. It is pg_dumpall causing it?
Please try to find out.
> Now I inadvertently blew away that user postgres and I can't co
I had two identical postgres users in my pg_users table. (Why does that
keep occurring? I also had to versions of each table I made.)
Now I inadvertently blew away that user postgres and I can't connect to
anything anymore. That is because there were no other users yet.
I even blew away the data
several of you reading these lists may remember my server locking up
problem -- we have 20 users on a linux rh kernel 2.2.2, postgres 6.4.2,
odbc Version='06.40.0005', front end all msaccess97, and the server would
lock up continually. actually postgres would lock up. the server was
perfectl
