On 6/17/07, Andrej Ricnik-Bay <[EMAIL PROTECTED]> wrote:
On 6/18/07, John K Masters <[EMAIL PROTECTED]> wrote:
> I feel somewhat embarrassed to post this but I can't get past the first
> post with Postgresql. I have installed onto a Debian testing system,
> created a space for the database clust
Hopefully your pg_hba.conf files look more like:local all all trusthost all all 192.168.10.0/24 trusthost pgbench all
192.168.3.0/24 trustOn 27 Sep 2006 21:02:47 -0700, blackjadelin <
[EMAIL PROTECTED]> wrote:I have co
On 10/20/06, Jean-Christophe Roux <[EMAIL PROTECTED]> wrote:
Hello,[snip]
none
of them will be inserted because the first insert is a primary key
violation. How can I have postgreSQL not mind about the error and
proceed to the next insert. I could send the inserts one at a time but
bundling them
On 24 Nov 2006 04:43:02 -0800, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I just can't understand the use of this PGDATA variable!
-I am on FC3. (pgl 7.4)
-I am installing rpms and then running /etc/init.d/postgresql start
(which is done by default)
-The resulting "data" directory is in
On 1/30/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
This has been discussed about ten thousand times, and the answer is
still no.
How did we go from this?
To this:
It's already in the TODO list.
regards, tom lane
Perhaps we should be more diplomatic in our appr
This is a little vague...There is a way to recover the data. Make postmaster come back up. Unless you're talking about postmaster not coming up due to corrupted data files, or a hardware failure.You do need to use pg_dump at regular intervals. It is common practice to back up data, after all.
No
Atomicity, Consistency, Isolation and DurabilitySee:http://cegt201.bradley.edu/projects/proj2003/equiprd/acid.html
On 1/5/06, John Meyer <[EMAIL PROTECTED]> wrote:
Okay, what exactly is ACID compliance?---(end of broadcast)---TIP 6: explain analyze is
