Greetings,
I've been using a PHP3+Postgres+Apache setup for about year now with almost no
problems, until now. Originally, it was setup on an ancient Sparc2 box w/
Solaris 2.6 w/ PHP+Postgres6.5.2+Apache1.3.9. My databases are modest, the main
table of one in particular has 5000 rows.
I recen
I think this is fixed in the current cvs tree. Can you grab a snapshot
ftp file and let me know. If not, can I get a contect diff. Thanks.
> Hi,
>
> I had a look over the JDBC-Driver and was able to remove the bug. It seems,
> that the formatting of the timestamp caused the malfunction. I'd
Max Pyziur <[EMAIL PROTECTED]> writes:
> NOTICE: AbortTransaction and not in in-progress state
> FATAL 1: The system is shutting down
That looks like a consequence not a primary failure. What's in the
postmaster log?
regards, tom lane
Marco Pratesi ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
pg_dump doesn't work on Linux PPC
Long Description
The description is very simple.
I am using PostgreSQL 7.0.2 on Yellow Dog Linux CS 1.2,
I use the official RPMs.
[EMAIL PROTECTED] wrote:
>
> Marco Pratesi ([EMAIL PROTECTED]) reports a bug with a severity of 1
> The lower the number the more severe it is.
>
> Short Description
> pg_dump doesn't work on Linux PPC
>
> Long Description
> The description is very simple.
> I am using PostgreSQL 7.0.2 on Yello
I have come across a query that produces different output depending on
weather or not an index is imposed on the relation. I am using
postgresql-7.0.2-2 installed as a binary from an rpm downloaded from the
postgres site. My machine is an Intel dual PII 300 with 256MB of ram.
The system runs Linux
What LOCALE setting do you run the postmaster in?
This looks like it might be the known problem with LIKE index
optimization not coping very well with non-ASCII collation orders.
(It tries, but if you have collation rules where multicharacter
patterns are treated specially, it tends to do the wro
Viktor Przebinda <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What LOCALE setting do you run the postmaster in?
> Output of the locale program is as follows:
> LANG=en_US
> LC_CTYPE="en_US"
> LC_NUMERIC="en_US"
> LC_TIME="en_US"
> LC_COLLATE="en_US"
> LC_MONETARY="en_US"
> LC_MESSAGES="en_US
Tom Lane wrote:
> I seem to recall something about another internationalization config
> file that might cause problems on RH6.2, particularly if you upgraded
> from an earlier release instead of doing a cold install of 6.2. But
> I'm not finding it in the archives right now. Anyone remember
> s
