Re: Odd duplicate database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Madison Kelly <linux(at)alteeve(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, postgres list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Odd duplicate database
Date: 2009-01-14 21:36:43
Message-ID: 22164.1231969003@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Madison Kelly <linux(at)alteeve(dot)com> writes:
> Alvaro Herrera wrote:
>> Please send along
>> select xmin, xmax, ctid, cmin, cmax, datname from pg_database;

> template1=# select xmin, xmax, ctid, cmin, cmax, datname from pg_database;
> xmin | xmax | ctid | cmin | cmax | datname
> ------+------+--------+------+------+------------
> 383 | 0 | (0,1) | 0 | 0 | template1
> 384 | 0 | (0,2) | 0 | 0 | template0
> 386 | 0 | (0,3) | 0 | 0 | postgres
> 659 | 0 | (0,10) | 0 | 0 | deadswitch
> 3497 | 3625 | (0,35) | 0 | 0 | nexxia
> (5 rows)

So the "nexxia" row did get updated at some point, and either that
transaction failed to commit or we've got some glitch that made this
row look like it didn't. Have you used any "ALTER DATABASE" commands
against nexxia?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Davis 2009-01-14 21:38:07 Re: A better BETWEEN for DATEs, TIMEs and TIMESTAMPs?
Previous Message Jeff Davis 2009-01-14 21:35:42 Re: A better BETWEEN for DATEs, TIMEs and TIMESTAMPs?