Skip site navigation (1) Skip section navigation (2)

Re: pgAccess change

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgAccess change
Date: 2000-03-31 14:44:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> Bruce Momjian wrote:
> > > Thanks.  I'm building a test RPM here so I can satisfy Tom's request for
> > > regress results on CURRENT.  My rpm patchset barfed on pgaccess -- so I
> > > investigated.  I fixed it in my local tree, but wanted to alert folk.
> > Glad you found it.  That was the one file I had to modify to get it to
> > match our old version, and obviously I messed that up.
> I'm going to take this opportunity to thank Marc for having a cvsweb
> interface -- as I was able to see when the difference was introduced
> using that interface.
> Given the number of things you patch, Bruce, it shouldn't surprise
> anyone that an occassional error is introduced -- that's why it's good
> to have many sets of eyes looking at the code.  I can only have
> nightmares about how many errors I could cause if I were applying
> patches at that rate... :-)

The problem with pgaccess is that is not a patch I can eyeball.  It is a
stand-alone tar file that writes over our files.  I am never sure what
is new or old until I see what files show as new, etc.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-hackers by date

Next:From: Vince VielhaberDate: 2000-03-31 14:45:47
Subject: Re: pgAccess change
Previous:From: Lamar OwenDate: 2000-03-31 14:36:30
Subject: Re: pgAccess change

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group