On Tue, 2010-08-31 at 14:13 -0400, Tom Lane wrote:
> Jeff Davis writes:
> > On Mon, 2010-08-30 at 20:06 -0400, Tom Lane wrote:
> >> You need extra_float_digits cranked up. Which pg_dump knows about.
>
> > I can't reproduce the problem with float4/8, but I still see a problem
> > with floating-po
Jeff Davis writes:
> On Mon, 2010-08-30 at 20:06 -0400, Tom Lane wrote:
>> You need extra_float_digits cranked up. Which pg_dump knows about.
> I can't reproduce the problem with float4/8, but I still see a problem
> with floating-point timestamps:
Hmmm ... timestamp_out pays no attention to ex
On Mon, 2010-08-30 at 20:06 -0400, Tom Lane wrote:
> 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
Robert Koch wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5632
> Logged by: Robert Koch
> Email address: expenda...@aemail4u.com
> PostgreSQL version: 8.4.4-1
> Operating system: Windows 2000 Pro
> Description:won't unistall properly
> Detail
David L Kensiski wrote:
> I though of that, but it's linked into the binary. Maybe this is a
> problem with the Sun build and not the code? How do I get in touch
> with the build maintainer?
Is there a README in the build install somewhere?
--
Fabien COELHO writes:
> The REFERENTIAL_CONSTRAINTS table in the information_schema references a
> constaint through its database/schema/name, but this information is not
> unique, so it may identify several constraints, thus the information
> derived may not be consistent.
Postgres does not e
Hello,
I haven't found a bug management system about postgresql, so here is a
mail. Maybe this issue was already reported, sorry if it is the case.
I have seen anything about the information_schema in pg todo list.
This is tested on postgresql 8.4.4.
The REFERENTIAL_CONSTRAINTS table in the
Dear all
Can someone tell me how to estimate the quality of my plan. For example if
the ideal query plan generated by Dynamic Programming has a plan quality of
1.0, and suppose I generate my query plan with some greedy method or
something, it will be worse (not as optimal as) than ideal plan by,
