On Wed, 2005-09-28 at 12:08 -0500, Kris Kiger wrote:
> My question then is, how do we tell which wal log is X (the one
> currently being written to)?
You don't say why you need to know?
If you really care, you can look at the status files in the
archive_status directory underneath pg_xlog. This
On Fri, 30 Sep 2005, Simon Riggs wrote:
You don't say why you need to know?
Not sure why Kris needs to know, but I need to know for PITR and keeping the
latest WAL file saved by a script which runs every few minutes as my client
does not turn over WAL files very often (about 4/day).
If yo
Thanks Rajesh.
Is this on TODO list? I think it's beneficial to be able to backup (or
oracle term, export) several tables (NOT only ONE) and restore (import)
back to another database for instance from a production DB to a
development or staging to prod, etc..) [This is doable in Oracle too
via th
1. create db by using postgres manager Lite's create db wizarddb
name new_db / host : lost host/port: 5432/login: postgreswhen I tried to
connect to this db I got FATAL error, ¡°database new_db doesn¡¯t exist."
The above suggest
that you haven't created your database (new_db) on the postg
> 1. create db by using postgres manager
Lite's create db wizard > db name new_db / host : lost host/port:
5432/login: postgres > when I tried to connect to this db I got
FATAL error, ¡°database new_db doesn¡¯t exist."
*** The above suggest that you haven't
created your database (new_d
On Fri, 2005-09-30 at 12:09, Tomeh, Husam wrote:
> 1. create db by using postgres manager Lite's create db wizard
>
> db name new_db / host : lost host/port: 5432/login: postgres
> when I tried to connect to this db I got FATAL error, ¡°database
> new_db doesn¡¯t exist."
Sounds like you created a
