The following bug has been logged online:
Bug reference: 1242
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.3
Operating system: Linux Debian 3.1
Description:Major bug in pgSQL
Details:
Hi,
apparently we have found a critical bug in pgSQL
The following bug has been logged online:
Bug reference: 1243
Logged by: Hanna Tapani
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.2
Operating system: Solaris
Description:Driver problem
Details:
SQLException: Something unusual has occured to cause t
PostgreSQL Bugs List wrote:
Problem: in some cases we experience the following problem - we have found
in the database some _absolutely_ identical rows, despite the fact, that we
have defined some unique (!) indexes on some of the fields and even primary
(!) keys, we can see, that the rows are
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> When you are experiencing this show us the result of this query:
> select cmax, cmin, xmax, xmin, * from where ;
Also, please, the ctid and oid columns (but leave out oid if you made
the table WITHOUT OIDS).
Also, if the condition is one that will no
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> How does this fix that case?
> It doesn't. This is why the second version of the patch was required,
> per http://archives.postgresql.org/pgsql-patches/2004-09/msg00039.php.
Okay, I've applied the right version of the patch now ;-)
The following bug has been logged online:
Bug reference: 1244
Logged by: Fernando del Valle
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Windows XP
Description:Postgres doesn't work on FAT
Details:
Postgres installs fine on W2
Hello,
in the release notes there is a "FAT is not really supported" notice
for PostgreSQL.
I suggest following workaround:
create a cacls.exe and put it first in the search path. That cacls.exe
should just return "OK" no matter of the imput-params.
Be warned that "FAT is not really supported"
Harald Armin Massa wrote:
Hello,
in the release notes there is a "FAT is not really supported" notice
for PostgreSQL.
I suggest following workaround:
create a cacls.exe and put it first in the search path. That cacls.exe
should just return "OK" no matter of the imput-params.
Be warned that "FAT is
Hello
We have a problem with one of our central databases and we need your
help to find a solution.
--
* Description:
--
"PosgreSQL is crashing with a signal 11 and we do not think is a
hardware problem" :(
Since last week, we are having a big problem wit
Rafael Martinez Guerrero <[EMAIL PROTECTED]> writes:
> * Information from CORE dump we got with --enable-debug. We have
> compiled a new version of postgres and run it through gdb with the core
> dump we had/got from postgres without --enable-debug.=20
Okay, theoretically that works, but it might
On Tue, 2004-09-07 at 19:58, Tom Lane wrote:
> Rafael Martinez Guerrero <[EMAIL PROTECTED]> writes:
> > * Information from CORE dump we got with --enable-debug. We have
> > compiled a new version of postgres and run it through gdb with the core
> > dump we had/got from postgres without --enable-de
On Tue, 2004-09-07 at 23:36, Tom Lane wrote:
> Rafael Martinez <[EMAIL PROTECTED]> writes:
> > I got this from one of our developers (from the core dump generated by
> > 7.3.7 without --enable-debug):
>
> > (gdb) inspect *att[i]
> > $3 = {attrelid = 0, attname = {data = '\0' ,
> > alignmentDummy =
Rafael Martinez <[EMAIL PROTECTED]> writes:
>> Hmm, what do you get from "x/10 3054556648" ?
> (gdb) x/10 3054556648
> 0xb610d5e8: 0x2f0c 0x0002 0x3017 0x020c6172
> 0xb610d5f8: 0x 0x 0x00ae 0x0006002b
> 0xb610d608: 0x2f1c0913
Rafael Martinez <[EMAIL PROTECTED]> writes:
> I got this from one of our developers (from the core dump generated by
> 7.3.7 without --enable-debug):
> (gdb) inspect *att[i]
> $3 = {attrelid = 0, attname = {data = '\0' ,
> alignmentDummy = 0}, atttypid = 1700, attstattarget = -1, attlen = -1,
> at
14 matches
Mail list logo
