-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
|
| OK i am posting my full script [ its not heavy programming i guess :) ]
| shall be grateful if you/someone could review it . (its well
commented i think)
| script also carries sample data.
|
| it does following
|
Hi,
Is there any way to get the date of creation of a database in Postgres?
Does postgres store this information in any system table.
If anybody have any idea about this please let me know. I need to find
out the creation date of one of my database.
Thanks,
Pradeep
On Thu, Mar 30, 2006 at 02:05:24PM +0530, Pradeep Sharma wrote:
Is there any way to get the date of creation of a database in Postgres?
Does postgres store this information in any system table.
I'm not aware that the creation time is stored anywhere (except
perhaps in query logs) but you might
On Thu, 30 Mar 2006, Michael Fuhr wrote:
On Thu, Mar 30, 2006 at 02:05:24PM +0530, Pradeep Sharma wrote:
Is there any way to get the date of creation of a database in Postgres?
Does postgres store this information in any system table.
I'm not aware that the creation time is stored
On Thu, Mar 30, 2006 at 05:20:00PM +0530, Pradeep Sharma wrote:
Thanks for the reply. But I guess there is some communication gap between
me and you regarding this topic. As I understood from your reply is, you
are talking about the date of Postgres setup/installation/upgrade.
No, I was
On Thu, Mar 30, 2006 at 05:27:12AM -0700, Michael Fuhr wrote:
Try a command like the following:
% ls -lt $PGDATA/base/*/PG_VERSION
You should see that each database has a copy of this file and that
each file has a different modification time (some might be within
a few seconds of each
On Thu, 30 Mar 2006, Michael Fuhr wrote:
On Thu, Mar 30, 2006 at 05:20:00PM +0530, Pradeep Sharma wrote:
Thanks for the reply. But I guess there is some communication gap between
me and you regarding this topic. As I understood from your reply is, you
are talking about the date of
Thanks anyways
From: Rajesh Kumar Mallah [EMAIL PROTECTED]
To: Salem Berhanu [EMAIL PROTECTED]
CC: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] postgres and persistant connections (using
Apache::DBI)
Date: Thu, 30 Mar 2006 09:29:35 +0530
since it is not a postgresql issue
i think we
lmyho [EMAIL PROTECTED] writes:
In more detail, the logs looks like:
...
imcomplete startup packet
received fast shutdown request
shuttingdown
database system is shut down
logger shutting down
Something like this, each has a little different, but ends the same way.
This is not a server
Hi,
I'm running 8.1.x on FC2 with smp.
The docs claim that pg_dump should allow normal operation of the db with the
exception of things like 'VACUUM FULL'.
Last night during backup, I noticed that I could not get a connection, either
remotely via jdbc or locally via psql. Well perhaps that is
Steve Linabery [EMAIL PROTECTED] writes:
Last night during backup, I noticed that I could not get a connection, either
remotely via jdbc or locally via psql. Well perhaps that is inaccurate: 'ps
-ef' showed several processes with a status message of waiting to startup
(or something similar;
On Thu, Mar 30, 2006 at 11:14:37AM -0500, Tom Lane wrote:
Steve Linabery [EMAIL PROTECTED] writes:
Last night during backup, I noticed that I could not get a connection,
either remotely via jdbc or locally via psql. Well perhaps that is
inaccurate: 'ps -ef' showed several processes with a
lmyho [EMAIL PROTECTED] writes:
In more detail, the logs looks like:
...
imcomplete startup packet
received fast shutdown request
shuttingdown
database system is shut down
logger shutting down
Something like this, each has a little different, but ends the same way.
This is
lmyho wrote:
The last one (successful bootup and shutdown):
pg_log# more postgresql-2006-03-30_103237.log
2006-03-30 10:32:37 CSTLOG: database system was shut down at 2006-03-30
10:32:20
CST
2006-03-30 10:32:37 CSTLOG: checkpoint record is at 0/33B96C
2006-03-30 10:32:37 CSTLOG: redo
On Thu, 2006-03-30 at 11:10, Chris Travers wrote:
lmyho wrote:
The last one (successful bootup and shutdown):
pg_log# more postgresql-2006-03-30_103237.log
2006-03-30 10:32:37 CSTLOG: database system was shut down at 2006-03-30
10:32:20
CST
2006-03-30 10:32:37 CSTLOG: checkpoint
Steve Linabery [EMAIL PROTECTED] writes:
I just replicated the problem, see below for explanation, but here is ps
output:
postgres 25817 3201 55 10:20 ?00:02:54 postgres: postgres
db_being_dumped [local] COPY
postgres 27956 3201 46 10:24 ?00:00:36 postgres:
--- Chris Travers [EMAIL PROTECTED] wrote:
lmyho wrote:
The last one (successful bootup and shutdown):
pg_log# more postgresql-2006-03-30_103237.log
2006-03-30 10:32:37 CSTLOG: database system was shut down at 2006-03-30
10:32:20
CST
2006-03-30 10:32:37 CSTLOG: checkpoint record
Hi
This is the scenario:
Export schema only
On a different postgres box,
drop the existing database, recreate the database and run psql with the
exported schema file.
One of the views did not
import. I get an error saying relation view-name does not exist
I
If you su postgres, can you run pg_ctl and get the database up by itself?
By the way, I can run pg_ctl to start the db server only after I links to the
data
directory. Debian's auto startup doesn't go this way but by the it's own
scripts.
leo
Interesting Database starts up at 10:32:37 and processes all
databases through autovacuum.
Then exactly a minute later, it processes the postgres database.
5 seconds later, you get a SIGINT.
Is there something wrong with autovacuum? Normally I would doubt it but
the
On Thu, 2006-03-30 at 11:38, lmyho wrote:
If I remember correctly, this is a problem with the debian startup
script requiring trust for the postgres superuser, and was discussed
sometime last year. I'll wander through the archives in a free moment
and see if I can find it.
Great
Great Scott!! Thank you!! This system was just installed on Debian (2
days),
and
the original pg_hba.conf file authen method was ident sameuser and
appears not
allow it to be changed!
Look forward to your information!! Thanks a lot!!
Can't find the thread right now (my
If by broken connection you are referring to the invalid startup
packet lines - that has been known to be caused by pretty much anything
other than a postgresql client connecting to the pg server port, ie
portscanner, someone telnetting, net bot, etc.
Jason Minion
-Original Message-
If by broken connection you are referring to the invalid startup
packet lines - that has been known to be caused by pretty much anything
other than a postgresql client connecting to the pg server port, ie
portscanner, someone telnetting, net bot, etc.
Do you actually mean the incomplete
Can you provide exact error messages here? You're not giving us a lot
of detail to go on...
On Mar 30, 2006, at 11:30 AM, Sriram Dandapani wrote:
Hi
This is the scenario:
Export schema only
On a different postgres box, drop the existing database, recreate
the database and run psql
25 matches
Mail list logo
