Alvaro Herrera wrote:
Laszlo Nagy wrote:
PostgreSQL 8.3.5, the system is now stable (uptime > 10 days).
PostgreSQL stats collector uses 100% CPU forever:
Could you grab a few stack traces from it and post them? Also possibly
useful, leave strace running on the pgstat process for a wh
Laszlo Nagy wrote:
> Alvaro Herrera wrote:
>> Laszlo Nagy wrote:
>>
>>> PostgreSQL 8.3.5, the system is now stable (uptime > 10 days).
>>> PostgreSQL stats collector uses 100% CPU forever:
>>>
>>
>> Could you grab a few stack traces from it and post them? Also possibly
>> useful, leave
It was 78816 and you traced 78815? Are you sure the process with 24h of
CPU was pgstat?
I'm sorry that was a typo. Of course I traced the good process (proof is
that at the end it renamed a file to "global/pgstat.stat".
And yes, "top" showed 24H in the TIME column and 99% in the WCPU colu
What I'm hearing is that I have to perform a base backup on my master in
Mass. after recovery completes, send that over a secure network
To Virginia, and lay it down there. Simple enough but the time to travel
Over the network becomes an issue - 12 - 13 hours at best.
If we have to do this then we
On Fri, 2008-12-19 at 09:14 -0500, Mark Steben wrote:
> What I'm hearing is that I have to perform a base backup on my master in
> Mass. after recovery completes, send that over a secure network
> To Virginia, and lay it down there. Simple enough but the time to travel
> Over the network becomes a
On Thu, 2008-12-18 at 16:43 -0500, Mark Steben wrote:
> 3. I am currently in a state where a log got partially copied and
> postgres
> cannot find a valid checkpoint to restart. What is the best way to
> remedy
> this situation? Pg_resetxlog perhaps?
Now, pg_resetxlogs, but in future don't dele
On Fri, 2008-12-19 at 08:51 -0800, Joshua D. Drake wrote:
> On Fri, 2008-12-19 at 09:14 -0500, Mark Steben wrote:
> > What I'm hearing is that I have to perform a base backup on my master in
> > Mass. after recovery completes, send that over a secure network
> > To Virginia, and lay it down there.
>>> "Mark Steben" wrote:
> What I'm hearing is that I have to perform a base backup on my master
in
> Mass. after recovery completes, send that over a secure network
> To Virginia, and lay it down there.
I'm not sure we're understanding each other. I was suggesting that
you needed to make a ne
Thanks for the clarifications Kevin, Josh, Simon
I am trying out Kevin's suggestion to create a second standby copy now.
I know I have to create the base copy and send it over, at least
For the first time to start recovery. I will look at rsync to do that.
Thanks for all the help -- Mark
I'm not
Have a question concerning how OID's are generated and assigned to tables in
postgres.
The application I inherited relies upon the oid's for primary keys.
I am currently in process of migrating our current Postgres Database from one
server [Postgres version 7.2] to another server [version 8.1.9
"Lipker, Joseph" writes:
> The application I inherited relies upon the oid's for primary keys.
It'd be a good idea to move away from that.
> The question is, after reloading the 7.2 version into the 8.19 version,
> should the migrated database be starting with the 20319 as last oid and
> t
11 matches
Mail list logo
