Look at:
http://zeoslib.sourceforge.net/
Adam
P.S. And remember, that You can use libpq.DLL too - the fastest way to
work with PostgreSQL.
Mario Jose Canto Barea pisze:
why are you can make a good database relational server
as postgresql 8.1, and dont make a rad/ide open source
for programming
"George Wilk" <[EMAIL PROTECTED]> writes:
> When and by what process is the history file being created? My standby
> server seems to be looking for it when put back in the recovery mode, after
> functioning as primary for a while.
> How should I handle missing history file in my script?
History f
POLONKAI Gergely wrote:
> We are currently developing a server cluster, and we are thinking of
> using PostgreSQL as our database backend. As I haven't found any
> information about this on the web (maybe I searched on the wrong
> keywords), I ask here: is it possible to run one database on multipl
I have most entries split over several lines:
Jun 29 19:56:40 db.xxx.xxx postgres[10640]: [5-1] DB=XXX U=XXX H=1.1.1.1
16854186.2190 idleLOG: Verbindungsende: Sitzungszeit: 0:01:22.10
Jun 29 19:56:40 db.xxx.xxx postgres[10640]: [5-2] Benutzer=xxx Datenbank=
Host=1.1.1.1 port=23640
Is it p
>>> On Fri, Jun 29, 2007 at 12:29 PM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
>> Tom Lane <[EMAIL PROTECTED]> wrote:
>>> Offhand I would recommend the same strategy for any requested filename
>>> that's not a plain WAL segm
"Radhika Sambamurti" <[EMAIL PROTECTED]> writes:
> Postgres-8.2.0 built successfully. But when I do an ldd on postgres I see
> that it is linking to the wrong openssl and crypto libraries.
> ...
> Instead it is pulling from the /lib (default red-hat) location rather than
> /usr/local/lib.
If you t
"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> wrote:
>> Offhand I would recommend the same strategy for any requested filename
>> that's not a plain WAL segment file (ie, all hex digits).
>
> I suspect that it's worth waiting for something like this, too?:
> 00010
>>> On Fri, Jun 29, 2007 at 11:47 AM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> History files are only created when you do a PITR recovery that stops
> short of the end of WAL (ie, you gave it an explicit stopping point
> criterion). So basically they never appear e
Hi,
I was running postgres-7.4.2 and upgraded to 8.2.0
Postgres-8.2.0 built successfully. But when I do an ldd on postgres I see
that it is linking to the wrong openssl and crypto libraries.
engpc17 bin]# ldd postgres
libssl.so.4 => /lib/libssl.so.4 (0x0091e000)
libcrypto.so.4
>>> On Fri, Jun 29, 2007 at 9:52 AM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
>> Just ignore 0001. Recovery will work fine even if absent. Don't
>> ignore all history files though, just that one. Hmmm, come to think of
>>
Tom,
When and by what process is the history file being created? My standby
server seems to be looking for it when put back in the recovery mode, after
functioning as primary for a while.
How should I handle missing history file in my script?
Cheers,
~george
-Original Message-
From: Tom
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> Just ignore 0001. Recovery will work fine even if absent. Don't
> ignore all history files though, just that one. Hmmm, come to think of
> it, why is it requesting it at all? We should just skip that request.
No, because then people would misdesign t
On Fri, 2007-06-29 at 09:57 -0400, George Wilk wrote:
> Thanks, Simon. I will ignore the request for the history file in my
> recovery_command from now on.
>
> Is the timeline history file needed when trying to put the standby server
> back into the recovery mode, after it assumed the primary rol
Thanks, Simon. I will ignore the request for the history file in my
recovery_command from now on.
Is the timeline history file needed when trying to put the standby server
back into the recovery mode, after it assumed the primary role? (i.e.
standby server goes *live*, and is subsequently restar
Hi,
I was running postgres-7.4.2 and upgraded to 8.2.0
Postgres-8.2.0 built successfully. But when I do an ldd on postgres I see
that it is linking to the wrong openssl and crypto libraries.
engpc17 bin]# ldd postgres
libssl.so.4 => /lib/libssl.so.4 (0x0091e000)
libcrypto.so.4 =>
On Fri, 2007-06-29 at 07:55 -0400, George Wilk wrote:
> My warm standby server is looking for a history file when booting up.
> It is looking for 0001.history file to be exact.
Just ignore 0001. Recovery will work fine even if absent. Don't
ignore all history files though, just that one.
My warm standby server is looking for a history file when booting up. It is
looking for 0001.history file to be exact. Since my *live* server
doesn't produce such file, I create an empty 0001.history file in the
archive directory and that seems to satisfy this requirement allowing the
sta
Tom,
You nailed it right in the head! My bad... My exit code was causing the
problem. Once I changed it to 1 the recovery mode exited and the database
came up:
waiting for file: 000100F2
--- trigger found ---
--- exiting recovery mode ---
exiting with 1
LOG: could not open fil
18 matches
Mail list logo
