Jon Colverson <[EMAIL PROTECTED]> writes:
> So, I think the problem is that exitArchiveRecovery() should be marking
> the restored log file as ".done" (or perhaps not bothering to restore
> the log file at all?).
> This looks like a bug to me. Any thoughts?
I don't think that will fix it. The
maintenance_work_mem = 1048576 (I have 9GB ram on this server).
Chris
On 5/30/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Chris Hoover" <[EMAIL PROTECTED]> writes:
> I am getting the following error when trying to run a reindex on one of
my
> databases.
> reindexdb: reindexing of database "xxx"
"Chris Hoover" <[EMAIL PROTECTED]> writes:
> maintenance_work_mem = 1048576 (I have 9GB ram on this server).
You might have that much RAM, but I wonder how much of it the kernel
will give to any one process. Did you check the ulimit settings the
postmaster is running under? Is it possibly a 32-b
On Thu, May 31, 2007 at 05:30:20PM +1200, adey wrote:
> HP was providing CA (Continuous Access) software that was claimed to provide
> WAN SAN replication by repeating IO in exactly the sequence it was generated
> on the master, to the slave.
The CA stuff, or anything else built on FCIP, is prett
Sorry for not providing that info Here are the ulimits for my postgres
account:
[EMAIL PROTECTED] ~]$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked
Thanks for your reply.
Tom Lane wrote:
Jon Colverson <[EMAIL PROTECTED]> writes:
So, I think the problem is that exitArchiveRecovery() should be marking
the restored log file as ".done" (or perhaps not bothering to restore
the log file at all?).
This looks like a bug to me. Any thoughts?
"Chris Hoover" <[EMAIL PROTECTED]> writes:
> This is on a 32bit dual HT Xeon system using the official rpms.
Um. I suspect you can't usefully set maintenance_work_mem as high as
1Gb in a 32-bit environment. Last I heard, the max address space
available to userland in 32-bit Linux is 3Gb (the ker
I'm currently doing EnterpriseDB training at a well-known
entertainment company. I found out something yesterday that I thought
the community would find interesting...
In their game (MMORPG) databases, they have fields on all their
tables that indicate whether a record has been deleted or n
Jim Nasby wrote:
I'm currently doing EnterpriseDB training at a well-known entertainment
company. I found out something yesterday that I thought the community
would find interesting...
In their game (MMORPG) databases, they have fields on all their tables
that indicate whether a record has be
Hello,
I have a problem with postgresql recovery. I want to make a test
recovery from our production server to a test machine. On the production
server runs PostgreSQL 8.0.3. On the test machine the PostgreSQL version
is 8.0.4 (installed from binary rpm).
I issued pg_start_backup and make a file s
It finally reoccurred. Here's what I got from attaching to those processes
from gdb. I attached with the postmaster binary, let me know if I should use
something else.
vero(su): ps axvw | grep notify
24556 ?Ss 0:03 0 3265 41262 29672 0.7 postgres: jerel
csdb chef(36275) notify
On Thu, May 31, 2007 at 09:23:01AM -0700, Joshua D. Drake wrote:
> Right. Where we just mark the row as dead and have to vacuum. We just
> delay the pain ;).
They've delayed the pain too. This is actually an illustration of
what Tom Lane said recently -- that the strategy of paying the cost
of m
You may want to give the latest version of 8.0 a try 8.0.13.
Ken
On Thu, May 31, 2007 at 06:14:05PM +0200, Sipos Ferenc wrote:
> Hello,
>
> I have a problem with postgresql recovery. I want to make a test
> recovery from our production server to a test machine. On the production
> server runs Po
Hello,
Thank you very much, its solved my problem. :)
From log file:
[...]
2007-05-31 19:39:49 CEST () (29313): LOG: redo done at 41/B0FFDB68
2007-05-31 19:39:49 CEST () (29313): LOG: restored log file
"0001004100B0" from archive
2007-05-31 19:39:49 CEST () (29313): LOG: archive rec
On 5/31/07, Andrew Sullivan <[EMAIL PROTECTED]> wrote:
They've delayed the pain too. This is actually an illustration of
what Tom Lane said recently -- that the strategy of paying the cost
of maintenance outside the main transaction path is intrinsically
superior, because you don't have to pay i
On 5/31/07, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
Or, you just use the features you pay for and use COMMIT NOWAIT.
Doh! Got mixed up on the conversation, that wouldn't help. But you
could use Oracle's in-memory UNDO, which would not be as costly as a
normal update.
--
Jonah H. Harris, S
Just curious, what sort of field do they use to mark the rows? I'm assuming
a timestamp since it would half to be part of the primary key, or am I way
off? This has really gotten me thinking about how I might implement this in
my database.
Thanks,
Chris
On 5/31/07, Jim Nasby <[EMAIL PROTECTED
"Sipos Ferenc" <[EMAIL PROTECTED]> writes:
> I have a problem with postgresql recovery. I want to make a test
> recovery from our production server to a test machine. On the production
> server runs PostgreSQL 8.0.3. On the test machine the PostgreSQL version
> is 8.0.4 (installed from binary rpm).
Chris Hoover wrote:
Just curious, what sort of field do they use to mark the rows? I'm
assuming a timestamp since it would half to be part of the primary key,
or am I way off? This has really gotten me thinking about how I might
implement this in my database.
Thanks,
Chris
I do this on
On Tuesday 29 May 2007 09:58, Joshua Kramer wrote:
> Also note that RedHat does PostgreSQL training:
>
> https://www.redhat.com/training/developer/courses/rdb147.html
>
> Note, however, that this is "RedHat Database" training. "RedHat Database"
> was a rebranded PostgreSQL 7.3.4 introduced back ar
20 matches
Mail list logo
