Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ... - Mailing list pgsql-committers

From Robert Haas
Subject Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...
Date
Msg-id AANLkTimJ-GQ1a9EbwuG8QvvXSfjtHECytbTK=BWibbZM@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Wed, Dec 29, 2010 at 12:10 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew Dunstan <andrew@dunslane.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 ...

git revert would give you an extra commit.  Andrew was speaking of git
reset, which can be used to undo a commit.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-committers by date:

Previous
From: Magnus Hagander
Date:
Subject: pgsql: Add REPLICATION privilege for ROLEs
Next
From: Robert Haas
Date:
Subject: pgsql: Support unlogged tables.