On 30 Sie, 20:10, t...@sss.pgh.pa.us (Tom Lane) wrote:
> wstrzalka writes:
> > finally I press up arrow to reexecute and that causes "Segmentation
> > fault" and psql to exit
>
> That would be a problem in libreadline, not in our code. There was
> somebody else complaining of a bug in Solaris' re
Tom Lane wrote:
Alex Zepeda writes:
I'd be happy to provide someone with a copy of the dump...
but it's ~70MB bzip'd.
I'd be willing to take a look ... but if my WAG is right, the insertion
order would be critical information to reproduce the problem. Is it
possible to tell what order the ro
Alex Zepeda writes:
> I'd be happy to provide someone with a copy of the dump...
> but it's ~70MB bzip'd.
I'd be willing to take a look ... but if my WAG is right, the insertion
order would be critical information to reproduce the problem. Is it
possible to tell what order the rows were inserted
Tom Lane wrote:
Alex Zepeda writes:
If I try to manually add the constraint on the table I get:
blockface=# alter table bus_positions add constraint "exclude_time_buffer" EXCLUDE USING gist
(vehicle WITH =, buffer_time WITH &&, bbox_dup WITH &&);
NOTICE: ALTER TABLE / ADD EXCLUDE will create
Alex Zepeda writes:
> If I try to manually add the constraint on the table I get:
> blockface=# alter table bus_positions add constraint "exclude_time_buffer"
> EXCLUDE USING gist (vehicle WITH =, buffer_time WITH &&, bbox_dup WITH &&);
> NOTICE: ALTER TABLE / ADD EXCLUDE will create implicit in
On Mon, 2010-08-30 at 19:40 -0400, Tom Lane wrote:
> That's really *not* supposed to happen, assuming that both machines have
> IEEE float arithmetic and competently written float I/O code.
On my machine I see:
=> select float4in(float4out((1::numeric + 1e-7::numeric)::float4)) =
(1::numeric
Jeff Davis writes:
> On Mon, 2010-08-30 at 19:40 -0400, Tom Lane wrote:
>> That's really *not* supposed to happen, assuming that both machines have
>> IEEE float arithmetic and competently written float I/O code.
> On my machine I see:
> => select float4in(float4out((1::numeric + 1e-7::numeric):
Jeff Davis wrote:
Are you using any floating point values, or floating-point timestamps
(that's a compile-time option)?
I'm using whatever the default compile time options are.
It's worth noting that if I delete the row, and then attempt to insert
a row with the same data on the original data
Jeff Davis writes:
> On Mon, 2010-08-30 at 14:05 -0700, Alex Zepeda wrote:
>> I dumped a table with an exclude constraint with pg_dump, and loaded it
>> into another instance of postgres where it promptly failed to create the
>> constraint. The complaint was... key conflicts with key. IOW,
>>
Alex Zepeda writes:
> I dumped a table with an exclude constraint with pg_dump, and loaded it
> into another instance of postgres where it promptly failed to create the
> constraint. The complaint was... key conflicts with key. IOW,
> duplicate data.
> This should not happen, correct? If it
On Mon, 2010-08-30 at 14:05 -0700, Alex Zepeda wrote:
> Short version:
>
> I dumped a table with an exclude constraint with pg_dump, and loaded it
> into another instance of postgres where it promptly failed to create the
> constraint. The complaint was... key conflicts with key. IOW,
> dupli
I'm relatively unsure where and how to proceed.
Short version:
I dumped a table with an exclude constraint with pg_dump, and loaded it
into another instance of postgres where it promptly failed to create the
constraint. The complaint was... key conflicts with key. IOW,
duplicate data.
Thi
wstrzalka writes:
> finally I press up arrow to reexecute and that causes "Segmentation
> fault" and psql to exit
That would be a problem in libreadline, not in our code. There was
somebody else complaining of a bug in Solaris' readline just recently
:-(. Might be worthwhile to install your own
I'm having problems with psql. Looks like bug.
Steps to reproduce on my box (100% segfaults):
#psql -U postgres -d mydb
$EXPLAIN ANALYZE SELECT .
after 20s I'm getting a plan & at the end there is smth like "stdin:
END"
then I press ENTER and I have back psql console\
finally I press up arrow
"Jaseb Betts" writes:
> /pgsql/src/timezone/tznames/Default/ doesn't include CAT
The reason that that's a user-configurable file is that it's impossible
to satisfy everybody :-(. Just add the abbreviations you use locally.
regards, tom lane
--
Sent via pgsql-bugs maili
The following bug has been logged online:
Bug reference: 5634
Logged by: Jaseb Betts
Email address: ja...@free.net.nz
PostgreSQL version: 8.3
Operating system: Windows xp 32 bit
Description:timezone/trigger issue
Details:
/pgsql/src/timezone/tznames/Default/ doesn't
16 matches
Mail list logo
