On Sat, Feb 21, 2009 at 12:14 AM, Guillaume Lelarge
wrote:
> Tino Schwarze a écrit :
>> [...]
>> I'm going to pg_restore a database dump of about 220 GiB (uncompressed,
>> but most data is BLOBs). The machine has 8 GiB of memory and 8 cores.
>> Is there any advice to speed up restoring, postgresql
[email protected] writes:
> I had a hardware problem this morning, which I believe is now resolved, but
> I seem to have a little database corruption issue. This is what I am seeing
> when I restart postgres:
> PANIC: right sibling's left-link doesn't match
8.2.6 and later provide a little more
Greetings,
I had a hardware problem this morning, which I believe is now resolved, but
I seem to have a little database corruption issue. This is what I am seeing
when I restart postgres:
PANIC: right sibling's left-link doesn't match
So I attempted to reindex the database and now I ge
Hi Peter,
Thanks for your reply and idea. I was up way
past my bed time and my mind was not with my
finger tips. As I followed suggestions from
Scott, I was able to get it to work fast. More
often than not, I push the door, when it is
written on the door: "PULL" :)
Regards,
Tena Sakai
-
Hello,
Tena Sakai wrote:
> I just finished installing postgres 8.3.6 and was
> able to start it. The log file reads:
>
> [2009-02-22 00:27:01.824 PST] < 11543 2009-02-22 00:27:01 PST >LOG:
> database system was interrupted; last known up at 2009-02-22 00:25:04 PST
> [2009-02-22 00:27:01.8
Of course, Deepak!
I had made an alias for "pg_ctl start ..." and always
had -D setting as /usr/local/pgsql/data. I have been
relying on this alias so much, I completely forgot
that's how actually it gets done.
Thank you.
Regards,
Tena Sakai
[email protected]
-Original Message-
F
Many thanks, Scott.
> Just stop your 8.3.3 and start 8.3.6 in the same data directory.
My set up is that I have a fair size partition named /pgsql.
In it, I have subdirectories such as 830, 833, and 836. As
I move from one rev to another, I basically make a link from
that directory (in my latest
First make sure you stop the 8.3.3 / 8.3.6 server and then start 8.3.6
server and point the data path to 8.3.3 data path.
/usr/postgres/8.3.3/bin/pg_ctl -D /usr/postgres/8.3.3/data/pgsql8.3.3 stop
/usr/postgres/8.3.6/bin/postgres -i -D /usr/postgres/8.3.3/data/pgsql8.3.3
>logfile 2>&1 &
Enjoy
On Sun, Feb 22, 2009 at 2:32 AM, Tena Sakai wrote:
> Hi,
>
> I am able to revert back to 8.3.3 system. Maybe
> I can use 8.3.3 psql to read the dumpall output.
> How can I direct the output to data directory of
> 8.3.6 postgres?
You don't have to dump and restore for a minor point update. Just
Hi,
I am able to revert back to 8.3.3 system. Maybe
I can use 8.3.3 psql to read the dumpall output.
How can I direct the output to data directory of
8.3.6 postgres?
Regards,
Tena Sakai
[email protected]
-Original Message-
From: Tena Sakai
Sent: Sun 2/22/2009 1:03 AM
To: Tena Saka
Hi,
I realized what's going, but still don't know what to do.
What's happening is that there is no pg_user table in my
new postgres, which is the problem I was going to attack
via psql. So this seems like a catch 22.
What can I do?
Tena Sakai
[email protected]
-Original Message-
F
Hi everybody,
I just finished installing postgres 8.3.6 and was
able to start it. The log file reads:
[2009-02-22 00:27:01.824 PST] < 11543 2009-02-22 00:27:01 PST >LOG:
database system was interrupted; last known up at 2009-02-22 00:25:04 PST
[2009-02-22 00:27:01.825 PST] < 11543 2009-0
12 matches
Mail list logo
