Title: postgresql 7.4.6 - FATAL Database Startup Message
Database System startup message
In postgres version 7.4.6, I notice that sometimes when the database starts up, it outputs a log message such as "2005-01-18 14:44:13 FATAL: the database system is starting up". Shouldn't this be "LOG"
Hi Guys,
I would really appreciate if someone could bring the light to this. Thank
you in advance. Here's my story:
postgresql-7.4.6
Linux Red Hat 9.0
I'm trying as anyone who ever installed Postgresql optimize it for speed.
After reading all those articles about increasing shared memory and twe
On Sun, Jan 23, 2005 at 01:47:53PM -0500, Mitchell Laks wrote:
> Could i create a database trigger to run a script like
> system("scp $filename $destination");
> where $filename is extracted from the entry just made into the database, and
> $destination is my other pc?
You can use procedural la
Mitchell Laks <[EMAIL PROTECTED]> writes:
> I would like my server to immediately "scp" the file to another machine, as
> soon as the application updates the table with the new entry.
> But when i look for sample triggers on the web they seem to only do things
> internal to the database (change
On Fri, Jan 21, 2005 at 08:43:00AM -0700, Haron, Charles wrote:
> Yes, but how do you escape the quote when the value of the string isn't know
> until the function is run?
>
> If $rma_data->{\'company_name\'} is returning Bob's Fixit at run time, how
> do escape the quote BEFORE Perl interprets t
Hi.
I have a postgresql database backed application. As soon as the application
stores a file on my server, it creates a entry in a table LOCATION_TABLE
which stores the file location in the table in my postgresql database (eg. in
LOCATION_TABLE in database MASTER).
I have read about triggers
