Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...
Date: 2010-12-29 05:10:18
Message-ID: 1586.1293599418@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 12/28/2010 11:50 PM, Tom Lane wrote:
>> Think I'll use -n in future.

> Would not git reset have undone the faulty commit if necessary?

Possibly. I looked at git revert, concluded it wouldn't do what
I wanted, and just went with an additional commit. Still learning
the tool ...

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2010-12-29 10:08:50 pgsql: Add REPLICATION privilege for ROLEs
Previous Message Andrew Dunstan 2010-12-29 05:01:05 Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...