Hello,
After about a year and a half of use, I ran into a peculiar problem
with my PostgreSQL driven app and I would like to understand why.
I have a web app that uses PostgreSQL 6.5.2 on the backend. The app logic
is Java beans and JSP. The OS is RedHat 6.2 i386. Anyways, there are two
ide
The following two SQL Exceptions are popping up after several days or
weeks of seemingly smooth execution:
"Unknown Response Type x" <= where x is a random ASCII character
and
"The column index is out of range"
Once one of these two SQL Exceptions start occurring, pretty much all
queries af
appens on 3 of my 4 machines on a monthly
> basis. This really needs to be fixed because vacuum won't run without
> the serial fields being unique.
>
> All of the above running 6.5.3
>
> Andy
>
> On Sat, 18 Dec 1999, Robin's Postgres List Archive wrote:
>
&g
Hi Folks,
When I write a query with a "WHERE" claused constrained by the "OR"
operator, postgresql creates the enormous pg_sorttemp~ files in
~pgsql/data/base/dbName/ that basically eat up all remaining disk space in
a matter of seconds. These files are 1.8GB+ by the time the partition is
full.
Problem solved, thank you for the responses!
Yes, I had run initdb as outlined in the instructions.
Then I received a tip from someone on the list suggesting:
"do: rpm -qa | grep postgres
then, for each package it returns: rpm -e "
Which I did. At that point, running createdb gave me a *new* e
