On Thu, 2005-02-10 at 02:37 +, Brian B. wrote:
> I am loading some spam/ham data/tokens, to be used for the dspam anti-spam
> software, into PostgreSQL. After a few hours of inserting and updating the
> existing data, the backend crashes with a signal 10 (bus error). I am also
> running an ANAL
The following bug has been logged online:
Bug reference: 1473
Logged by: Brian B.
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: FreeBSD 4.11-STABLE
Description:Backend bus error, possibly due to ANALYZE
Details:
Hello,
I am loading so
The following bug has been logged online:
Bug reference: 1472
Logged by: Joachim Schuette
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Win2k
Description:Win-Installation failed due to missing access-rights
Details:
I ran the installat
On Wed, 9 Feb 2005 12:27:13 +0100
Michael Meskes <[EMAIL PROTECTED]> wrote:
> Thanks for the report and the patch. I just committed it to CVS HEAD and
> the 8.0 branch. 7.4 does not suffer from this bug.
Probably, "create sequence" and "create domain" have same problems. Here's
a patch for prepr
Summary: Index scans to enforce a unique index do not show up in pg_stats
Severity: Very Annoying
Verified On: 7.4.3, 7.4.6, 8.0.1
Description:
Index scans on the index of a unique constraint in order to verify uniqueness
of inserted rows do not show up in the pg_stats views. This is a proble
Yea, we have never supported loading newer dumps into older servers. We
do support the opposite, though.
---
Tobias Brox wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1468
> Logged by:
"Sergey Koshcheyev" <[EMAIL PROTECTED]> writes:
> I'm trying to optimize "is null" queries, since PgSQL doesn't index null
> values. I have found that creating an expression index on (column is null)
> could work, but it doesn't get used unless the index expression is part of a
> comparison. Could
The following bug has been logged online:
Bug reference: 1470
Logged by: Sergey Koshcheyev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6
Operating system: Linux (Debian)
Description:Boolean expression index not used when it could be
Details:
I'm trying
The following bug has been logged online:
Bug reference: 1471
Logged by: Sergey Koshcheyev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6
Operating system: Linux (Debian)
Description:Corrected e-mail address - bug 1470
Details:
Sorry for this dummy repor
Lucas Galfaso wrote:
Create a trigger using capitalized letters. Whenever you select the trigger,
the name of the trigger appears without quotes.
Fixed for 1.2.1, thanks for reporting.
Regards,
Andreas
---(end of broadcast)---
TIP 7: don't forget to
On Wed, Feb 09, 2005 at 04:34:01PM +0900, TANIDA Yutaka wrote:
> ecpg on 8.0.x crashes while compiling "create table as" statements. For
> example,
> ...
> Here's a patch attached.
Thanks for the report and the patch. I just committed it to CVS HEAD and
the 8.0 branch. 7.4 does not suffer from thi
On Mon, Feb 07, 2005 at 11:48:48PM +, Anthony COMMUNIER wrote:
> The statement : EXEC SQL DELETE FROM WHERE CURRENT OF
> (describe in SQL 99) isn't recognize by ecpg
This holds for the backend as well, doesn't it?
The feature is not implemented and thus it makes no sense to allow it in
ecp
> If you have the time, it would be interesting to dump out the rows with
> pg_filedump (see http://sources.redhat.com/rhdb/). I usually use
> "pg_filedump -i -f" to get the most useful display. Looks like you need
> to dump pages 3, 5, and 7 of that table to see all three rows.
I have the resu
13 matches
Mail list logo
