Christof Petig schrieb:
So I propose the following hack (feel free to improve it!) to go into
mainline. Since only powerpc and amd64 are affected (and the old method
does not work at all here at all) the patch should not be controversial.
I failed to mention that call by reference is the default
NB: The crossposting is actually suggested on the mailing list description:
"If you've found a bug in PostgreSQL, please send it both to this list
and also to the pgsql-patches list."
Amd64 and powerpc share an ABI design which enables variable passing in
registers and which makes va_list a complex
Tom Lane schrieb:
Christof Petig <[EMAIL PROTECTED]> writes:
Commenting out "set extra_float_digits=2" in pg_dump.c gives me the old
behaviour. Is it only me wishing for a command line parameter for
pg_dump to set desired precision?
It seems to me that you should be using typ
Tom Lane schrieb:
Christof Petig <[EMAIL PROTECTED]> writes:
COPY test (x) FROM stdin;
0.2
\.
This is not a bug; it's pg_dump trying to recreate the actual floating
point value as accurately as it can. See the discussion of
extra_float_digits from six months or a ye
I didn't believe it at first:
create table test ( x double precision);
insert into test values (0.3);
test=# select * from test;
x
-
0.3
--
-- Data for TOC entry 3 (OID 53248)
-- Name: test; Type: TABLE DATA; Schema: public; Owner: christof
--
COPY test (x) FROM stdin;
0.2
[EMAIL PROTECTED] wrote:
> Ing. Pavel Janousek ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> ECPG, cursors and transactions
>
> Long Description
> When I use ECPG in transactions I got some bad results - I think that t
The severity of this bug heavily depends on your lack of buggy programs.
Short description:
Long standing open transactions combined with high traffic updates and
some regular vacuums eventually corrupt memory.
Long description:
Due to a design flaw within our ecpg Programs (I don't recommend
de
[EMAIL PROTECTED] wrote:
> Martin Kuria ([EMAIL PROTECTED]) reports a bug with a severity of 1
> The lower the number the more severe it is.
Bug? severe?
But I will undertake to answer you though.
> Short Description
> how to copy data from excel spreadsheet to postgresql database
>
> Long Desc
Martin Neimeier wrote:
> Hello,
> some additional informations:
>
> - if i execute the subselect alone, it works fine !.
> - The same select statement works with sybase and oracle, so i think its a legal
>statement.
> - After reading in the sql2-standard, i have found nothing which restricts uni
