From the postgreSQL docs:
16.7. Secure TCP/IP Connections with SSL
19.1. The pg_hba.conf file
19.2. Authentication methods
19.2.1. Trust authentication
19.2.2. Password authentication
19.2.3. Kerberos authentication
19.2.4. Ident-based authentication
19.2.5. PAM Authenticati
Lookas as if you've managed to turn off your computer mid-transaction
thereby corrupting the postgreSQL commit logs (pg_clog)...
You should never just turn off a database server... always shut it down
normally... Turning it off was a major mistake. I dont know if you can
recover or not as the s
Are you possibly running logrotate on the postgreSQL server logs ? Logrotate
is usually set to signal (SIGHUP) the log owner (in this case -- postgreSQL)
after rotating the log file...
You normally can't just delete the logfiles and expect postgreSQL to
continue wherever you left it... you norm
CREATE TABLE mytable (
id serial not null primary key,
myvalue varchar(50),
create_dt timestamp not null default now()
);
INSERT INTO mytable (myvalue) VALUES ('When was this record inserted ?');
SELECT * FROM mytable;
"Si" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECT
it doesnt work that way this is postgreSQL -- a relational database.
you can't just copy the data directory like you can with mySQL or DBase, or
BTrieve or any of the "old-school" databases... if you need to backup and
restore data you need to look at pg_dump and pg_dumpall and the impor
Way overkill... all you really need is a decently sized (160G or a pair of
80's) hard-disk and a P-III / AMD Athlon 750 MHz with 512MB Ram and FreeBSD
5 and postgreSQL
With databases... it's all about disk-performance anyway...
""Michael D. Sofka"" <[EMAIL PROTECTED]> wrote in message
ne
What about putting a "RAISE NOTICE" statement inside each of your child
functions ?
"Mario Splivalo" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Dobar dan! (Means 'good day' in Croatian)
>
> I have a postgres (plpgsql) function that calls other (plpgsql and sql)
> functions. T
Why would you want two servers on the same box ??? There's this thing called
"schemas" within one database... and postgreSQL is very capable of managing
multiple databases from the same server
If you insist on trying to run two postgreSQL server on teh same box -- You
also need to make sure
and from the shell prompt: you can find ALL postgreSQL process id's by:
%>ps ax | grep postgres
""Eduardo J. Ortega"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> You can also kill the postgres process corresponding to the hung query. do
> NOT
> kill -9. Only kill. Postgres
I recently discovered that another programmers CGI's are occasionally
killing my postgreSQL server so I decided to modify the postgres.conf file
to do some extended logging and additionally redirect the server output into
an error log (using the -l pgdblog.log) switch...
postgreSQL was restarted l
"Tom Lane" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> "codeWarrior" <[EMAIL PROTECTED]> writes:
> > I noticed that the server generated logfile gets real big real fast --
(15
> > queries and it'
Are you connecting on the "localhost" -- I saw no entry in your
pg_hba.conf for localhost...
Also -- Was postgres STARTED with -i or did you just change the pgoptions
file and NOT restart your postgres server or reload the options file ???
pg_ctl RELOAD...
""Sill-II, Stephen"" <[EMAIL PROT
12 matches
Mail list logo
