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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 11:14:17
Message-ID: AANLkTimJ-GQ1a9EbwuG8QvvXSfjtHECytbTK=BWibbZM@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Dec 29, 2010 at 12:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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 ...

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2010-12-29 11:49:31 pgsql: Support unlogged tables.
Previous Message Magnus Hagander 2010-12-29 10:08:50 pgsql: Add REPLICATION privilege for ROLEs