Hi, - see below
Plugge, Joe R. wrote:
Change the shbang line to match where your php in installed (if it is at
all)
#!/full_path_to_my_php -q
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Carol Walter
Sent: Thursday, September 25, 2008 1:15 PM
To: S
Hi Everybody,
About 1.5 month ago, my machine (which runs redhat linux
2.6.9-78.0.1.ELsmp on Dell hardware with postgres 8.3.3)
had a terrible crash. I am mostly recovered, but there
is at least one more thing that's not right.
Namely, when the machine gets rebooted, postgres doesn't
s
On Thu, Sep 25, 2008 at 1:42 PM, Tena Sakai <[EMAIL PROTECTED]> wrote:
> Hi Everybody,
>
> About 1.5 month ago, my machine (which runs redhat linux
> 2.6.9-78.0.1.ELsmp on Dell hardware with postgres 8.3.3)
> had a terrible crash. I am mostly recovered, but there
> is at least one more thing that'
Hi Everybody,
About 1.5 month ago, my machine (which runs redhat linux
2.6.9-78.0.1.ELsmp on Dell hardware with postgres 8.3.3)
had a terrible crash. I am mostly recovered, but there
is at least one more thing that's not right.
Namely, when the machine gets rebooted, postgres doesn't
start autom
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> On Thu, Sep 25, 2008 at 10:09 AM, BJ Taylor
> <[EMAIL PROTECTED]> wrote:
>> PANIC: right sibling's left-link doesn't match: block 175337 links to
>> 243096 instead of expected 29675 in index "dbmail_headervalue_3"
>> STATEMENT: INSERT INTO dbmail_head
On Thu, Sep 25, 2008 at 10:09 AM, BJ Taylor
<[EMAIL PROTECTED]> wrote:
> PANIC: right sibling's left-link doesn't match: block 175337 links to
> 243096 instead of expected 29675 in index "dbmail_headervalue_3"
> STATEMENT: INSERT INTO dbmail_headervalue (headername_id, physmessage_id,
> headerval
Change the shbang line to match where your php in installed (if it is at
all)
#!/full_path_to_my_php -q
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Carol Walter
Sent: Thursday, September 25, 2008 1:15 PM
To: Steve Crawford
Cc: Scott Marlowe; pgsql-adm
Hi Steve,
That's a cool way to do it. I wish I thought of it.
Here's yet another way by java:
public class lotsofhex55 {
public static void main (String[] argv) {
char myHex55;
myHex55 = (char) 0x55;
// replace 256 with 262144 af
Well, it was a bit convoluted, but I created the file with Excel,
filling the right number of cells with \x55. This worked too. The
script wouldn't run for me. I got an error about a "bad interpreter".
Carol
On Sep 25, 2008, at 1:40 PM, Steve Crawford wrote:
Scott Marlowe wrote:
I used
Scott Marlowe wrote:
I used this very simple little php script to make this
filename: mk55:
#!/usr/bin/php -q
Or, using standard *nix tools (Note: 0x55 = ascii U):
dd bs=1k count=256 if=/dev/zero | tr '\000' U > full_of_0x55
Cheers,
Steve
--
Sent via pgsql-admin mailing list (pgsql-admi
"Aras Angelo" <[EMAIL PROTECTED]> writes:
> We have been running our database server without any problem or reboot at
> all for a year. Yesterday we needed to change servers so we went ahead and
> installed the same postgresql version (8.2.1), restored the database files,
> ran some tests offline.
"BJ Taylor" <[EMAIL PROTECTED]> writes:
> Here are some recent logs from our system. Unfortunately, I didn't think to
> grab the logs at the time I killed those processes, and now they are gone.
> I found those processes by using ps, and then I killed them with a simple
> kill *processid*. Here a
Hello,
We have been running our database server without any problem or reboot at
all for a year. Yesterday we needed to change servers so we went ahead and
installed the same postgresql version (8.2.1), restored the database files,
ran some tests offline. Everything was good. As soon as we launch
Hey Tom,
Here are some recent logs from our system. Unfortunately, I didn't think to
grab the logs at the time I killed those processes, and now they are gone.
I found those processes by using ps, and then I killed them with a simple
kill *processid*. Here are samples of our current log files:
"BJ Taylor" <[EMAIL PROTECTED]> writes:
> We are using version 8.3.1. And to be precise, when I started the vacuum
> (analyze), I started it as a cron job to run daily around midnight. The
> next day I came in and checked on it and it was still running. Not thinking
> that it would take more tha
We are using version 8.3.1. And to be precise, when I started the vacuum
(analyze), I started it as a cron job to run daily around midnight. The
next day I came in and checked on it and it was still running. Not thinking
that it would take more than a full 24 hours to run, I let it be, and the
n
On Thu, Sep 25, 2008 at 1:59 AM, Claus Guttesen <[EMAIL PROTECTED]> wrote:
> Hi.
>
> I found out by accident that my db-dump, at least in ver. 8.3.3,
> automagically converts from iso-8859-1 to utf-8. Our db has been
> around since January 2000 and iso-8859-1 was chosen back then as
> encoding. Whe
Hi.
I found out by accident that my db-dump, at least in ver. 8.3.3,
automagically converts from iso-8859-1 to utf-8. Our db has been
around since January 2000 and iso-8859-1 was chosen back then as
encoding. When I occasionally imported the nightly dump to a test-db
it would complain very early d
19 matches
Mail list logo
