I had a problem using PITR recovery just now. If I do:
SELECT pg_start_backup('label');
do my tar
SELECT pg_stop_backup();
and stop the server, delete /data, then recover from the tar, delete
files in pg_xlog, then set recovery.conf to restore, it fails, I think
because n
In parse_func.c there are routines argtype_inherit() and
gen_cross_product() that date from Berkeley days. The comments
explain their reason for existence thus:
* This function is used to handle resolution of function calls when
* there is no match to the given argument types, but there might
Did you not see the posts by Richard and Dennis?
ElayaRaja S wrote:
Hi,
I am unable to restart the PostgreSQL. I am using redhat Linux 9
with postgresql 7.4.5. Unexpectedly due to ups problem my server was
shutdown once. After that i am unable to restart the server. How to
stop and start.
Present s
On Mon, Mar 28, 2005 at 11:22:20AM -0500, Tom Lane wrote:
> So far I've been very pleased with the low defect rate against 8.0.
> Most of the bugs we have fixed were either in new features, or were
> pre-existing problems that also occur in 7.4 or even further back.
As usual, I've been remiss late
>> Tom, assuming we fix this, are you fine with the concept?
>
>Mostly. Should the --with-krb-srvnam configure parameter go away?
>Or is it now seen as establishing an installation default? (Either
>way implies some documentation work.)
The original way kept it in there to establish an installat
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Tom, assuming we fix this, are you fine with the concept?
Mostly. Should the --with-krb-srvnam configure parameter go away?
Or is it now seen as establishing an installation default? (Either
way implies some documentation work.)
>> I'd like to vote in favor of this patch:
>> http://candle.pha.pa.us/mhonarc/patches2/msg00025.html.
>
>> I know Tom said he didn't really like it, but I'd ask you to
>reconsider
>> that.
>
>The patch is unacceptable as is because (a) it adds a libpq
>configuration parameter that acts different
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> I'd like to vote in favor of this patch:
> http://candle.pha.pa.us/mhonarc/patches2/msg00025.html.
> I know Tom said he didn't really like it, but I'd ask you to reconsider
> that.
The patch is unacceptable as is because (a) it adds a libpq
configu
On Fri, Apr 15, 2005 at 12:54:24PM -0400, Tom Lane wrote:
> falcon <[EMAIL PROTECTED]> writes:
> > I think It would be useful to cache return values for stable
> > and immutable functions. Now thay are really called everytime.
>
> In most circumstances the overhead of searching such a cache would
falcon <[EMAIL PROTECTED]> writes:
> I think It would be useful to cache return values for stable
> and immutable functions. Now thay are really called everytime.
In most circumstances the overhead of searching such a cache would swamp
any benefit we might get from it.
reg
On Thu, Apr 14, 2005 at 06:36:44PM +0100, Simon Riggs wrote:
> I'd suggest a move right probability of 97% (divide by 16) for itemsz >
> 16 bytes and 94% (divide by 32) when itemsz >= 128
>
> Though I think functional indexes are the way to go there.
Why?
On a somewhat different note, what about
On Fri, Apr 15, 2005 at 08:42:45AM +0100, Dave Page wrote:
> [pgsql-slavestothewww] Comment 2333 added to page install-upgrading.html of
> version 7.4
> Author: Shayne Hardesty <[EMAIL PROTECTED]>
>
> If you use pg_dump on an older version (say 7.1.x, 7.2.x, or 7.3.x) you will
> get complain
Hi!
I'd like to vote in favor of this patch:
http://candle.pha.pa.us/mhonarc/patches2/msg00025.html.
I know Tom said he didn't really like it, but I'd ask you to reconsider
that.
My use would be mainly for my integrate-with-active-directory project.
AD requires uppercase principal names, which
Hello, pgsql-hackers.
I think It would be useful to cache return values for stable
and immutable functions. Now thay are really called everytime.
Demonstration (Postgresql 8.0.1 SlackWare10.0):
create table t
(
i int PRIMARY KEY
) without oids;
insert into t values (1);
insert into t values (
I think we should add a new wal_sync_method that will use Darwin's
F_FULLFSYNC fcntl().
From :
#define F_FULLFSYNC 51 /* fsync + ask the drive to
flush to the media */
This fcntl() will basically perform an fsync() on the file, then flush
the write cache of the disk.
I'll att
This is *great* news. It's certainly going to help a lot in getting
legacy apps running on postgresql, where you can't change the actual
queries that are being run (or can but only after fighting about it for
hours and hours). And it'll do wonders to those who run "amateur
benchmarks" and then dete
Hi,
I am unable to restart the PostgreSQL. I am using redhat Linux 9
with postgresql 7.4.5. Unexpectedly due to ups problem my server was
shutdown once. After that i am unable to restart the server. How to
stop and start.
Present status is running. If i tried to start i am getting as
1) bash-2.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 14 April 2005 18:39
> To: Dave Page
> Cc: Greg Stark; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Interactive docs idea
>
> "Dave Page" writes:
>
> > We can get from 2 - 10 a day I would guess.
ElayaRaja S wrote:
Hi,
I am unable to restart the PostgreSQL. I am using redhat Linux 9
with postgresql 7.4.5. Unexpectedly due to ups problem my server was
shutdown once. After that i am unable to restart the server. How to
stop and start.
Present status is running. If i tried to start i am ge
On Fri, 15 Apr 2005, ElayaRaja S wrote:
> Hi,
> I am unable to restart the PostgreSQL. I am using redhat Linux 9
> with postgresql 7.4.5. Unexpectedly due to ups problem my server was
> shutdown once. After that i am unable to restart the server.
> DETAIL: The data directory was initialized by
20 matches
Mail list logo
