Achim =?iso-8859-1?Q?Kr=FCmmel?= <[EMAIL PROTECTED]> writes:
> I suppose this problem is easy to reproduce.
No, it isn't. At the very least, we need the full schema for the
table causing this.
regards, tom lane
---(end of broadcast)--
I am running a PostgreSQL 7.1.3 on a Intel Pentium III
My operating system is SuSE Linux 7.1 with Kernel 2.4.4 (ELF)
I compiled postgresql with gcc 2.95.2
My problem:
when using "vacuum analyze " on very large tables (I have one
with about 30GB) the memory usage increases continues until no memo
I took option 1 and managed to create a profile of a slow and a fast run:
The frequent functions of the FAST run:
% cumulative self self total
time seconds secondscalls Ts/call Ts/call name
0.00 0.00 0.00 15725437 0.00 0.00 Al
Andreas Wernitznig <[EMAIL PROTECTED]> writes:
> I took option 1 and managed to create a profile of a slow and a fast run:
It's difficult to compare these profiles, because they seem to be taken
over very different numbers of queries --- did you let the "fast" run
process more queries than the "s
Rainer Mager ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
timestamps cannot be created without time zones
Long Description
Creating a TABLE with a TIMESTAMP type seems to ignore the WITH TIME ZONE option. That
is, with or w
