Обсуждение: pgsql: Widen the money type to 64 bits.

Log Message:
-----------
Widen the money type to 64 bits.

Modified Files:
--------------
    pgsql/src/backend/utils/adt:
        cash.c (r1.68 -> r1.69)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/cash.c.diff?r1=1.68&r2=1.69)
    pgsql/src/include/catalog:
        pg_type.h (r1.176 -> r1.177)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_type.h.diff?r1=1.176&r2=1.177)
    pgsql/src/include/utils:
        cash.h (r1.23 -> r1.24)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/cash.h.diff?r1=1.23&r2=1.24)

This commit message is rather old, I remarked on its absence earlier, but
better late than never I guess ;)

On Tue, 2 Jan 2007, D'Arcy Cain wrote:

> Log Message:
> -----------
> Widen the money type to 64 bits.
>
> Modified Files:
> --------------
>     pgsql/src/backend/utils/adt:
>         cash.c (r1.68 -> r1.69)
>         (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/cash.c.diff?r1=1.68&r2=1.69)
>     pgsql/src/include/catalog:
>         pg_type.h (r1.176 -> r1.177)
>         (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_type.h.diff?r1=1.176&r2=1.177)
>     pgsql/src/include/utils:
>         cash.h (r1.23 -> r1.24)
>         (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/cash.h.diff?r1=1.23&r2=1.24)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>

--
He did decide, though, that with more time and a great deal of mental
effort, he could probably turn the activity into an acceptable
perversion.
        -- Mick Farren, "When Gravity Fails"

On Sun, 7 Jan 2007 21:04:09 -0800 (PST)
Jeremy Drake <pgsql@jdrake.com> wrote:
> This commit message is rather old, I remarked on its absence earlier, but
> better late than never I guess ;)

Not sure what you mean.  I just committed it recently.  I held off
until after the release as requested.  What do you mean by "old?"

--
D'Arcy J.M. Cain <darcy@druid.net>         |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.

D'Arcy J.M. Cain wrote:
> On Sun, 7 Jan 2007 21:04:09 -0800 (PST)
> Jeremy Drake <pgsql@jdrake.com> wrote:
> > This commit message is rather old, I remarked on its absence earlier, but
> > better late than never I guess ;)
>
> Not sure what you mean.  I just committed it recently.  I held off
> until after the release as requested.  What do you mean by "old?"

You committed it five days ago, because the date on the email was Jan 2,
but it only arrived today.  It should have appeard within minutes of the
commit.

--
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

> > > This commit message is rather old, I remarked on its absence earlier, but
> > > better late than never I guess ;)
> >
> > Not sure what you mean.  I just committed it recently.  I held off
> > until after the release as requested.  What do you mean by "old?"
>
> You committed it five days ago, because the date on the email was Jan 2,
> but it only arrived today.  It should have appeard within minutes of the
> commit.
>

i'm sure it got stuck in the maia filter (happens all the time with delays of a couple of hours up to several days) or
inthe moderator steve (if the sender  
was'nt on the list allow. can happen since it was a long time since he last committed). check the headers if you still
havethe original mail around to see  
where it stuck.

/Magnus