"Guido Barosio" <[EMAIL PROTECTED]> writes:
>I've just downloaded the 8.0.1 tar.gz from the argentina mirror (the one
> served via your web page).
>while trying to (post ./configure) run the make command, the program exit
> with a parse error on the line 2211, a '$' simbol is found where a
"Dennis van Dok" <[EMAIL PROTECTED]> writes:
> PostgreSQL version: 7.3.4
> Running a script through psql with ON_ERROR_STOP=1 will yield return value 3
> if the script ends with a C style comment (/*...*/).
This seems to be fixed in 7.4.* and later.
regards, tom lane
---
Joel Krajden <[EMAIL PROTECTED]> writes:
> If the indexes are created in fis_index, the foreign key constraints in the
> user table are ignored on insert and update.
Works for me...
$ mkdir /tmp/fis
$ mkdir /tmp/fis_index
$ psql regression
...
regression=# create tablespace fis location '/tmp/fi
Robert Creager <[EMAIL PROTECTED]> writes:
> "Dirk Raetzel" <[EMAIL PROTECTED]> confessed:
>> date_trunc('week', ...) returns the wrong week for first days in January if
>> their calendar week belongs to the previous week.
> I brought this up a couple of weeks ago in Hackers since I created this e
On Mon, 21 Mar 2005, Peter Cottingham wrote:
> Appears that the GROUP BY clause is not working correctly on new server
> (GROUP BY should order the result set in ASCENDING order, NOT DESCENDING
> order.) See below
I do not believe this is a bug. Result sets have no guaranteed ordering
unless yo
Michael Fuhr <[EMAIL PROTECTED]> writes:
> On Mon, Mar 21, 2005 at 07:20:04PM +, Peter Cottingham wrote:
>> Appears that the GROUP BY clause is not working correctly on new server
>> (GROUP BY should order the result set in ASCENDING order, NOT DESCENDING
>> order.) See below
> As far as I k
On Mon, Mar 21, 2005 at 07:20:04PM +, Peter Cottingham wrote:
>
> Appears that the GROUP BY clause is not working correctly on new server
> (GROUP BY should order the result set in ASCENDING order, NOT DESCENDING
> order.) See below
>
> **
> select dom_id, co
I believe that pg_autovacuum will work with a .pgpass file just like any
libpq based application.
Olivier Thauvin wrote:
The following bug has been logged online:
Bug reference: 1567
Logged by: Olivier Thauvin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating
When grilled further on (Fri, 25 Mar 2005 08:28:58 + (GMT)),
"Dirk Raetzel" <[EMAIL PROTECTED]> confessed:
>
> The following bug has been logged online:
>
> Bug reference: 1563
> Logged by: Dirk Raetzel
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Opera
Ingolf Knopf wrote:
> "java.sql.PreparedStatement.executeUpdate()" throws "java.sql.SQLException",
> if the prepared sql-string contains '?' within a C-like comment.
>
> Example:
> select relname
> from pg_class
> where /*relowner = ? and*/
> relname = ?
>
> In this case, the java.sql.
The following bug has been logged online:
Bug reference: 1555
Logged by: Peter Cottingham
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7-3.FC3.1
Operating system: Linix
Description:bug in GROUP BY?
Details:
Appears that the GROUP BY clause is not working
Have you tried an analyze after 1,000 or so inserts? Also, you should
be able to disable sequence scans for the duration of the connection
using SET enable_seqscan=false.
-Zeki
Brian O'Reilly wrote:
The following bug has been logged online:
Bug reference: 1552
Logged by: Brian O'
I have been fighting over this for 3 weeks - 3 weeks people - it's
unbelievable.
An rpm package should include all dependencies - why is this so difficult?
PG is a killer program, but what's the use if no one can get it installed.
This thing needs libreadline.so.5 why? why? why does it need it? w
The following bug has been logged online:
Bug reference: 1554
Logged by: Guido Barosio
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Red Hat Linux release 7.3 (Valhalla
Description:wrong character on the sjis_to_utf8.map file
Details:
The following bug has been logged online:
Bug reference: 1556
Logged by: Dennis van Dok
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.4
Operating system: Debian GNU/Linux 3.0
Description:psql ON_ERROR_STOP returns 3 when scripts ends in C
style comment
Deta
Josh Berkus wrote:
Brian,
They PGSQL-PERFORMANCE list is really the appropriate place for performance
issues like yours. Subscribe?
http://www.postgresql.org/community/lists
Yes, I will subscribe to the performance list, but strictly speaking the
behaviour described should be considered a bu
The following bug has been logged online:
Bug reference: 1560
Logged by: Joerg Ertl
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP Professional
Description:Service does not start
Details:
Error message are:
could not connect to
The following bug has been logged online:
Bug reference: 1557
Logged by: Staffan Sandberg
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6-1.FC2.2
Operating system: Fedora Core 2
Description:UPPER() and LOWER() do not return the right characters
Details:
H
The following bug has been logged online:
Bug reference: 1559
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.2, from rpm
Operating system: SuSE 9.1
Description:Typo in translation of postmaster
Details:
When try to delete a table which is refer
I have two tablespaces: fis (default) and fis_index. The users are required to
create the tables in fis and the indexes if fis_index.
If the indexes are created in fis_index, the foreign key constraints in the
user table are ignored on insert and update.
The constraints work properly if the ind
The following bug has been logged online:
Bug reference: 1558
Logged by: Cade Cairns
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: MacOSX 10.3.8
Description:memory leak in libpq connectDBStart()
Details:
The leak occurs when libpq can
Bruce Momjian wrote:
This is going to be a backward compatibility problem
You say that as if it's a bad thing.
In a previous thread, I think Bruce and Tom both commented on
ripping out some of the weird undocumented interval behavior:
http://archives.postgresql.org/pgsql-patches/2003-09/msg00134.
The following bug has been logged online:
Bug reference: 1561
Logged by: Ingolf Knopf
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: JDBC
Description:wrong detection of number of parameters in
java.sql.PreparedStatement
Details:
"java.s
The following bug has been logged online:
Bug reference: 1566
Logged by: Olivier Thauvin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Linux (Mandrake cooker)
Description:can't hide password with pg_autovacuum
Details:
I found an secur
The following bug has been logged online:
Bug reference: 1565
Logged by: Karl O. Pinc
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Linux CentOS 3.3
Description:SRPM does not rebuild due to krb5.h
Details:
I'm using CentOS 3.3 which is
The following bug has been logged online:
Bug reference: 1567
Logged by: Olivier Thauvin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Linux (Mandrake cooker)
Description:can't hide password with pg_autovacuum
Details:
I found an secur
The following bug has been logged online:
Bug reference: 1564
Logged by: Steinhaus, Harald
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.01
Operating system: Windows XP
Description:special Character OleDB
Details:
using charset SQL_ASCII German special char
The following bug has been logged online:
Bug reference: 1562
Logged by: Stefan Taube
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Windows XP Home
Description:OdbcDataAdapter.Update Fails
Details:
Hi,
the Update Command of an OdbcDat
The following bug has been logged online:
Bug reference: 1563
Logged by: Dirk Raetzel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2
(mingw-special)
Description:wrong week returnded by
Patrick Clery <[EMAIL PROTECTED]> writes:
> I have a partial index that contains a predicate to check for whether the
> field deleted is false or not:
> CREATE INDEX people_essays_any_essaytype_idx
> ON people_essays (person_id)
> WHERE NOT deleted;
> The following query does NOT use the in
I have a partial index that contains a predicate to check for whether the
field deleted is false or not:
CREATE INDEX people_essays_any_essaytype_idx
ON people_essays (person_id)
WHERE NOT deleted;
The following query does NOT use the index:
EXPLAIN ANALYZE
SELECT *
FROM people_essays
W
31 matches
Mail list logo
