| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Josh Berkus" <josh(at)agliodbs(dot)com>, "Bill Moran" <wmoran(at)potentialtech(dot)com> |
| Cc: | "Dave Page" <dpage(at)pgadmin(dot)org>,<pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Prepping to break every past release... |
| Date: | 2009-03-04 23:08:23 |
| Message-ID: | 49AEB587.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> You could always take a survey ... bosses love surveys ...
>
> Done: http://wwwmaster.postgresql.org/community/
Is there some assumed relationship between those options and whether
they'd like to see the names changed?
Also, it's hard to pick what option to choose there -- I typically
have cause about once or twice a month to poke around in those tables,
and we have development tools which reference these tables
directly....
I guess the closest option would be "access them all the time." I
hope that wouldn't be interpreted as supporting the proposed change.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2009-03-04 23:12:45 | Re: Prepping to break every past release... |
| Previous Message | Josh Berkus | 2009-03-04 23:07:52 | Re: Prepping to break every past release... |