Hi,
I have tried to taken backup while no one is connected. Should i change my
RAM and then check it. Version are same of pg_dump and database version 8.1.
Should I copy the data folder ? and then restore it with new installation or
what do you mean to say kindly brief it please. I will be
Tom,
I believe this is pretty much a show stopper for anyone using jdbc to
upgrade to 8.3.x.
Any word on 8.3.2 ?
Dave
On 31-Mar-08, at 7:26 PM, Tom Lane wrote:
While testing the changes I was making to Pavel's EXECUTE USING patch
to ensure that parameter values were being provided to the
Amit jain wrote:
Hello All,
We are using postgresql version 8.1 and our database size is 7gb. Ram Size
is 2 GB.
while trying to take backup through pg_dump i am getting following error.
oka97: pg_dump amtdb amtdb.out
pg_dump: ERROR: invalid memory alloc request size 4294967293
pg_dump:
Dave Cramer [EMAIL PROTECTED] writes:
Any word on 8.3.2 ?
Obviously, nothing is happening during PGCon ;-)
There was some discussion a week or so back about scheduling a set of
releases in early June, but it's not formally decided.
regards, tom lane
--
Sent via
Hi All,
Can this random order in archival of files be explained?
grep archived /var/log/localmessages
2008-05-23 08:43:43 PDTLOG: archived transaction log file
000109BD009D
2008-05-23 08:44:41 PDTLOG: archived transaction log file
000109BD00A0 - 9D and 9F
Hi,
From: David Fetter [EMAIL PROTECTED]
Subject: Re: [PATCHES] WITH RECURSIVE patch V0.1
Date: Sun, 18 May 2008 11:47:37 -0700
I tried a bunch of different queries, and so far, only these two
haven't worked. Any ideas what I'm doing wrong here?
WITH RECURSIVE t(n) AS (
SELECT 1
On Sat, May 24, 2008 at 03:21:01AM +0900, Yoshiyuki Asaba wrote:
Hi,
From: David Fetter [EMAIL PROTECTED]
Subject: Re: [PATCHES] WITH RECURSIVE patch V0.1
Date: Sun, 18 May 2008 11:47:37 -0700
I tried a bunch of different queries, and so far, only these two
haven't worked. Any ideas
I've been puzzled by a couple of recent buildfarm failures:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=dawn_batdt=2008-05-22%2006:00:01
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=vaquitadt=2008-05-19%2020:00:03
Both fail the timestamp test like this:
*** ./expected/timestamp.out
Hi,
From: David Fetter [EMAIL PROTECTED]
Subject: Re: [PATCHES] WITH RECURSIVE patch V0.1
Date: Fri, 23 May 2008 11:26:30 -0700
Where is the new patch?
I will create the revised patch on June.
This is a patch for this problem.
*** ../../pgsql/src/backend/executor/nodeRecursivescan.c
Tom Lane wrote:
Both of the observed failures are on Windows machines, where I'm told
that the resolution of gettimeofday() is an abysmal 55msec, so it
seems that the only surprise here is that we haven't seen the failure
often before.
Actually, reading up some more it seems the 55msec was
On Sat, May 24, 2008 at 05:01:11AM +0900, Yoshiyuki Asaba wrote:
Hi,
From: David Fetter [EMAIL PROTECTED]
Subject: Re: [PATCHES] WITH RECURSIVE patch V0.1
Date: Fri, 23 May 2008 11:26:30 -0700
Where is the new patch?
I will create the revised patch on June. This is a patch for this
Gurjeet Singh [EMAIL PROTECTED] writes:
Can this random order in archival of files be explained?
Maybe something wiped out the contents of the archive status
subdirectory? If the .ready files all went away, the backends would
eventually recreate them, but possibly in a surprising order.
Magnus Hagander [EMAIL PROTECTED] writes:
And I agree that it's strange we haven't seen it before. Could it be a
side-effect from something that happened lately, or should we consider
it purely random?
Well, it's possible we have seen it before and ignored it because it
wasn't reproducible.
Hi ,
I have tried to taken backup while no one is connected. Should i change my
RAM and then check it. Version are same of pg_dump and database version 8.1.
Yes try that . Though I dont think thats going to help. Just checking are
you using AMD server any chance .
Please provide complete
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
And I agree that it's strange we haven't seen it before. Could it be a
side-effect from something that happened lately, or should we consider
it purely random?
Well, it's possible we have seen it before and ignored it because
Hi,
I recently (on my flight to Ottawa) changed ecpg to use the keyword list
of the backend instead of its own. This means that there is one less
file to sync manually. However, it also means that an additional keyword
defined in the backend will break compilation as ecpg doesn't have this
Would anyone object to \df displaying a function's volatility? Maybe
limit it to \df+?
Ideally we would have a short header for the column so that it doesn't
take too much space, and specify the setting with a single letter. The
meaning of each letter we could display at the bottom of the table
Alvaro Herrera wrote:
Would anyone object to \df displaying a function's volatility? Maybe
limit it to \df+?
Ideally we would have a short header for the column so that it doesn't
take too much space, and specify the setting with a single letter. The
meaning of each letter we could display at
Hi all,
These patch implements the TODO item: Have psql show current values
for a sequence.
Comments are welcome.
* Credits
The original patch were developed by Euler Taveira de Oliveira
[EMAIL PROTECTED]
but how he is a little busy, he sends it to me and I made some changes
to satisfy
the TODO
Tom Lane [EMAIL PROTECTED] writes:
What I'm considering doing is putting a BEGIN/COMMIT around the whole
sequence, which will guarantee that now() does *not* advance, thus
eliminating the midnight gotcha. This would mean that the expected
output of the comparison to 'now' changes from 0 rows
[moved to -hackers, because talk is about implementation details]
I've ported the patch of Sushant Sinha for fragmented headlines to pg8.3.1
(http://archives.postgresql.org/pgsql-general/2007-11/msg00508.php)
Thank you.
1 diff -Nrub postgresql-8.3.1-orig/contrib/tsearch2/tsearch2.c
now
stucked with the function LexizeExec which I do not totally understand
(... and is not well documents too :) )
Sorry for that. LexizeExec() is a play around supporting thesaurus dictionary,
which is designed to replace phrase by phrase. So, if it see first matched word
then it asks the
On Sat, May 24, 2008 at 12:27:16AM -0300, Dickson S. Guedes wrote:
Hi all,
These patch implements the TODO item: Have psql show current values
for a sequence.
Comments are welcome.
Sequence public.foo_bar_seq
+---+-+-+
|Column |
23 matches
Mail list logo
