Re: [GENERAL] Future of PostgreSQL - Mailing list pgsql-general

From Sander Steffann
Subject Re: [GENERAL] Future of PostgreSQL
Date
Msg-id 003a01bf4fa9$bbd307a0$0201010a@chello.nl
Whole thread Raw
In response to Re: [GENERAL] Future of PostgreSQL  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [GENERAL] Future of PostgreSQL  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
Hi,

> > The 3 greatest technical/engineering challenges:  1) system
> > reliability & recoverability, 2) system reliability & recoverability,
> > and 3) system reliability and recoverability.
>
> And we don't have a problem in this area, do we?

At the moment, not realy, but a few things would be VERY nice:
- No need for a complete dump/restore on an major upgrade
- A pg_dump that ALWAYS can make a dump that can be restored without editing
it first
  (When a user had the access to create databases, creates some, and that
access is removed, the dump can't be restored anymore because it creates the
user without the rights to create databases, but somewhat later tries to
create a database with that user. I hope you understand this... :) I now
create all databases by hand as the superuser, and set the datdba myself.
- A dump program that can dump/restore large objects.

Don't get me wrong. I'm not complaining, and we work with PostgreSQL a lot
without any big problems. Just some ideas to make it easier for the
administrator.

And of course, thanks for all the work on PostgreSQL that makes it what it
is now, and a Merry Cristmas!
Sander Steffann.



pgsql-general by date:

Previous
From: Peter Berghold
Date:
Subject: Re: [GENERAL] DBI::Pg for Perl?
Next
From: Kevin Lo
Date:
Subject: Re: [GENERAL] DBI::Pg for Perl?