Re: [BUGS] Unexpected query results

"Miguel A. Juan" <[EMAIL PROTECTED]> writes: > SELECT * FROM diagnostics where codigo LIKE '103.%'; > the string in the like statment could be any code, including any character > in [ 'A' - 'Z', '.' , '0' - '9']. > With previous releases that returns all the records that 'codigo' begins > wi

Re: [BUGS] sanity check error for pg_dump

PRAGATI SAVAIKAR <[EMAIL PROTECTED]> writes: > We have recently started getting following error messages > failed sanity check, table arind was not found > failed sanity check, table inpart was not found > due to which pg_dump process does not get complete. It's a good bet that these tables bel

[BUGS] sanity check error for pg_dump

Currently we have upgraded postgres from 7.0.2 to postgres7.0.3 version on Linux 2.2.16-22smp #1 SMP 2000 i686 unknown . And we take backup of our postgres database on daily bases through cron using following scripts * # Script to backup the minx databases daymon="`date +%d``date +%b`" BA

Re: [BUGS] Table constraint ordering disrupted by pg_dump

Title: Re: [BUGS] Table constraint ordering disrupted by pg_dump I have loaded this new version and re-tested but don't see it fixed. If the standard regression tests are run and after completion a pg_dump is performed: pg_dump -o regression > dumpfile, if you look in the dumpfile, you will

[BUGS] to_char miscalculation on April Fool's Day - the start of daylight savings

Likely related to bug #249. I also entered this bug in the bug tool database Hello, It's April 3 and I'm developing an update routine to maintain expired records, some of which expired on April 1. When these records didn't get updated, I investigated and identified the alleged bug (which is

[BUGS] psql segmentation fault

I've been running Postgres on a Solaris 2.8 box for a long time. Just upgraded to 7.0.3 and noticed the reappearance of a bug that I've seen before: psql segfaults on startup. The problem is clearly and unmistakeably related to readline (psql -n works like a charm). I've tried mucking aroun

[BUGS] Unexpected query results

Hello, I've encountered with a problem running a query that with previous releases worked fine. Thats the query: SELECT * FROM diagnostics where codigo LIKE '103.%'; the string in the like statment could be any code, including any character in [ 'A' - 'Z', '.' , '0' - '9']. With previo

RE: [BUGS] Loosing files after backend crash

> The "relfilenode" attribute of the tuple contained the value > "326210". I tried to find the file with that name in the > database directory - it really was not there. Did you look in lost+found? > Thus, the backend crash has led not only to impossibility to > complete my task, but also to

RE: [BUGS] compilation error

> Iam installing postgresql-7.0.3 on solaris sparc 2.7. > > ... > > `/usr/share/src/postgresql-6.5.3/src/backend/lib' > make[1]: *** [lib.dir] Error 2 > make[1]: Leaving directory > `/usr/share/src/postgresql-6.5.3/src/backend' > make: *** [all] Error 2 Looks like there's a little version mixing

Re: [BUGS] compilation error

[EMAIL PROTECTED] writes: > stringinfo.c:115: `va_list' undeclared (first use in this function) Try changing src/include/c.h so that and are included unconditionally (near line 53) and remove #include near line 770. Or try 7.1RC2 or later --- these changes are already made for 7.1.

[BUGS] compilation error

suresh ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description compilation error Long Description Hi Iam installing postgresql-7.0.3 on solaris sparc 2.7. In that machine i installed flex, gnu-make ,readline and bison i installed.But