Re: Prepping to break every past release... - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Prepping to break every past release...
Date
Msg-id 49AEB587.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: Prepping to break every past release...  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Prepping to break every past release...  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
>>> Josh Berkus <josh@agliodbs.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


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Prepping to break every past release...
Next
From: Josh Berkus
Date:
Subject: Re: Prepping to break every past release...