Yup that sounds useful - would this be another column added to the
pg_stop_backup called wal_filename or similar?
My script uses this name to find the date/time of the current .backup
file and remove any files earlier than it (except obviously the one
listed in the START WAL LOCATION).
I've yet
Excellent addition. I suggest in 24.1 - Shared Disk Failover something
about the risk of having two postmasters come up on the same data
directory, which is entirely possible if the old master doesn't release
the disk in time.
On Tue, 2006-11-14 at 15:11 -0500, Bruce Momjian wrote:
I wrote
Hello, We are using (PostgreSQL) 8.0.1 for Solaris. Apparently ourpostgres users were wiped out somehow, for I cannot even log in assuperuser "postgres". Our pg_hba.conf settings are as loose as possible("trust"). This problem started mid session after we ran a .sql scriptto upgrade a DSpace
Hi, the new guy is back with another
question.
Regarding partitioning I set up a
testing table parent table and 4 partitioning childrens tables
inheriting the
Attributes of the parent. I inserted
1800 rows in all 450 equitably in each partition. The CHECK constraints
work great.
Will Cameron [EMAIL PROTECTED] writes:
We are using (PostgreSQL) 8.0.1 for Solaris. Apparently our
postgres users were wiped out somehow, for I cannot even log in as
superuser postgres. Our pg_hba.conf settings are as loose as possible
(trust). This problem started mid session after we
2006. November 8. 02.34 dátummal Michael McCloskey ezt írta:
Postgres is starting automatically for me at startup.
When I boot up my machine and then check the running processes I
see postmaster.exe and 4 postgres processes.
How can I stop this?
PGBIN=/usr/local/pgsql/bin;
