Tom, thank you very much for your excellent and fast analysis (I mean it
seriously, I am comparing your help to IBM Informix commercial support
:-) ).
It is possible that the corruption was caused by a HW problem at customer's
server, and then this problem appeared also at our development envi
On Tue, Aug 29, 2006 at 05:13:40PM -0600, Charlie Savage <[EMAIL PROTECTED]>
wrote:
>> Tom Lane wrote:
>>
>>> It appears that building a gin index on an empty table fails on any
>>> platform. I get a null pointer dereference with the following stack
>>> trace
> Teodor Sigaev wrote:
>
>> Fixed i
Well it would be a good idea to check the row validity. If the row is
partially corrupted, I can get an error (which is quite good) but I can get
bad results without an error as well, which is really bad.
After Tom decoded which row yields the problem, I tried to select the data
from the corru
The following bug has been logged online:
Bug reference: 2596
Logged by: Anderson Nonato Santos
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Windows 2003
Description:Invalid memory alloc request size
Details:
I have this error after a
Fixed in HEAD, thank you
Tom Lane wrote:
"Gin Indexes cause server to crash on Windows" <[EMAIL PROTECTED]> writes:
CREATE TABLE test (
vector tsvector NOT NULL
);
CREATE INDEX idx_test_vector ON test USING gin (vector);
server closed the connection unexpectedly
It appears that building a g
The following bug has been logged online:
Bug reference: 2597
Logged by: David
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: XP Home
Description:windows installer error
Details:
Hi,
I'm istalling postgresql on an xp (home) machine. Wh
For the sake of completeness/reference: The backport for 8.1
(http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/gin_tsearch2_81.gz)
doesn't seem to have this bug, at least on a linux x86_64 machine I can
create empty gin indexes with no problem.
It hasn't, because 8.2 already goes forward:
The following bug has been logged online:
Bug reference: 2598
Logged by: Andreas Langegger
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Gentoo Linux 3.3.6, Kernel 2.6.16
Description:Columns named R are not accessible - although R is not a
"Andreas Langegger" <[EMAIL PROTECTED]> writes:
> It seems that the column name "R" or "r" is reserved.
Hardly.
> If I want to insert tuples I get the error message:
> ERROR: column "r" of relation "xyz" does not exist
Worksforme:
regression=# create table xyz(r int);
CREATE TABLE
regression=
Andreas Langegger <[EMAIL PROTECTED]> writes:
> Well, I also tried your simple regression test and it worked. The more
> I'm wondering why this does not:
> CREATE TABLE sunspots
> ...
> "R" int2,
"R" with double quotes represents capital R, but when you write R
without quotes in a query, it's i
Backport also works fine on Windows and Linux x86_32 (Fedora Core 5).
Charlie
Bernhard Weisshuhn wrote:
On Tue, Aug 29, 2006 at 05:13:40PM -0600, Charlie Savage <[EMAIL PROTECTED]>
wrote:
Tom Lane wrote:
It appears that building a gin index on an empty table fails on any
platform. I get a
The following bug has been logged online:
Bug reference: 2599
Logged by: Josh Tolley
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Fedora Core 5
Description:AM/PM doesn't work in to_timestamp in the middle of a
string
Details:
eggyknap
The following bug has been logged online:
Bug reference: 2600
Logged by: Christopher Browne
Email address: [EMAIL PROTECTED]
PostgreSQL version: CVS HEAD (8.2)
Operating system: AIX 5.3
Description:dblink compile with SSL missing libraries
Details:
If I try to build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, I also tried your simple regression test and it worked. The more
I'm wondering why this does not:
CREATE TABLE sunspots
(
sunspots_key int4 NOT NULL,
- -- DEFAULT nextval('sunspot_seq'::regclass)
date date NOT NULL,
"time" time NOT NULL,
On Wed, Aug 30, 2006 at 10:18:46 +0200,
Filip Hrbek <[EMAIL PROTECTED]> wrote:
>
> It is possible that the corruption was caused by a HW problem at customer's
> server, and then this problem appeared also at our development environment
> because of the data already beeing corrupted. I will rec
Christopher Browne wrote:
The following bug has been logged online:
If I try to build dblink when PG is configured "--with-openssl", the build
of the contrib module dblink breaks as follows:
If I add, to the GCC command line, requests for libssl and libcrypto...
-lssl -lcrypto
e.g. - comm
Joe Conway wrote:
> Christopher Browne wrote:
>> The following bug has been logged online:
>
>>
>> If I try to build dblink when PG is configured "--with-openssl", the
>> build
>> of the contrib module dblink breaks as follows:
>
>> If I add, to the GCC command line, requests for libssl and libcr
[EMAIL PROTECTED] (Joe Conway) writes:
> Christopher Browne wrote:
>> The following bug has been logged online:
>
>> If I try to build dblink when PG is configured "--with-openssl", the
>> build
>> of the contrib module dblink breaks as follows:
>
>> If I add, to the GCC command line, requests for
18 matches
Mail list logo
