On Tue, Aug 26, 2008 at 7:16 AM, Janardhanachari, Jagadeesha
[EMAIL PROTECTED] wrote:
HI,
Thanks for your reply, but tell me what is the default password for
postgres on windows environment ?
Assuming you used the installer, whatever password you entered when
prompted. It won't let you
Hallo Craig,
Craig Ringer schrieb:
So: the user's report is incorrect in blaming pg_restore, but correct in
that comments on the public schema (and presumably other default schema)
aren't preserved by pg_dump | pg_restore. The real reason appears to be
that they're not dumped in the first
The following bug has been logged online:
Bug reference: 4376
Logged by: Cong
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: WindowXP
Description:Running as a database
Details:
Make it as a database but i don't know how to convert it
can you share the PostgreSQL version you are using
PG8.3.1
maybe you are facing some sort of corruption?
I do not know. All other works fine except that.
- Original Message -
From: Hans-Juergen Schoenig [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: pgsql-bugs@postgresql.org
Sent:
Thomas H. wrote:
maybe its by design (to not insert badly encoded characters into the
utf8 encoded logs)? nevertheless to debug those faulty programm/codes,
it would help to see what query provokes the error...
Well, the problem is mainly that there is no query, because the bytes arriving
are
Hello,
[note: in pastes below, the only thing changes are database names and
hostnames, for privacy reasons; otherwise plain cut'n'paste including
typos...)
Very short version: I cancelled a VACUUM FULL; server crashed; won't
start again because it tries to access an obsolete WAL log file that
Peter Schuller wrote:
The pg_xlog directory contains:
-rw--- 1 postgres postgres 16777216 Aug 26 17:16 0001001800EE
drwx-- 2 postgres postgres 305232 Aug 26 17:14 archive_status
Note that the archival of the ED xlog file started at 17:14:52,
and I cancelled
Peter Schuller wrote:
I will go hide in a corner now...
FWIW, as soon as you come out of the corner, you can solve the problem
easily by manually copying the file back from the archive location into
pg_xlog and restarting the server.
--
Alvaro Herrera
Peter Eisentraut [EMAIL PROTECTED] writes:
Thomas H. wrote:
maybe its by design (to not insert badly encoded characters into the
utf8 encoded logs)? nevertheless to debug those faulty programm/codes,
it would help to see what query provokes the error...
Well, the problem is mainly that
Zahid Khan [EMAIL PROTECTED] writes:
I see one behavior change is PG8.3 and PG 8.2 .I was getting error of
underflow value in PG8.2 when i
tried to insert '1E-307' in double precision column .And my
application was expecting the same error condition with the same
values against PG 8.3.3
Gregory Stark [EMAIL PROTECTED] writes:
Peter Eisentraut [EMAIL PROTECTED] writes:
Well, the problem is mainly that there is no query, because the bytes
arriving
are garbage. A human observer could make sense of it in some cases, but not
a computer in the general case.
How is that
On Tue, 2008-08-26 at 01:04 -0400, Tom Lane wrote:
Please provide some more detail about those experiments. The test case
hasn't been seen to fail in the buildfarm, AFAIR.
Dan Farina, my colleague at Truviso, was experimenting with some query
transformations that pushed the range table entries
Jeff Davis [EMAIL PROTECTED] writes:
= -- make foo into a subquery and add a no-op
= -- to prevent it from pulling up the subquery
= select max(a), generate_series(1,2) as g from (select a as a from foo
offset 0) dummy;
ERROR: set-valued function called in context that cannot accept a set
2008/8/26 Tom Lane [EMAIL PROTECTED]:
Jeff Davis [EMAIL PROTECTED] writes:
= -- make foo into a subquery and add a no-op
= -- to prevent it from pulling up the subquery
= select max(a), generate_series(1,2) as g from (select a as a from foo
offset 0) dummy;
ERROR: set-valued function called
14 matches
Mail list logo
