Re: remove separate postgres.(sh)description files

2020-01-19 Thread John Naylor
On Sun, Jan 19, 2020 at 7:58 PM Heikki Linnakangas wrote: > > > On Wed, Jan 08, 2020 at 02:33:23PM +0200, Heikki Linnakangas wrote: > >> Grepping around, there are a few stray references to > >> postgres.description still: > >> > >> $ git grep -r -I postgres.shdescript . > >> src/backend/catalog/.

Re: remove separate postgres.(sh)description files

2020-01-19 Thread Heikki Linnakangas
On 16/01/2020 23:39, Tomas Vondra wrote: On Wed, Jan 08, 2020 at 02:33:23PM +0200, Heikki Linnakangas wrote: On 31/12/2019 02:08, John Naylor wrote: I'm guessing the initial data for pg_(sh)description is output into separate files because it was too difficult for the traditional shell script t

Re: remove separate postgres.(sh)description files

2020-01-16 Thread Tomas Vondra
On Wed, Jan 08, 2020 at 02:33:23PM +0200, Heikki Linnakangas wrote: On 31/12/2019 02:08, John Naylor wrote: I'm guessing the initial data for pg_(sh)description is output into separate files because it was too difficult for the traditional shell script to maintain enough state to do otherwise.

Re: remove separate postgres.(sh)description files

2020-01-08 Thread Heikki Linnakangas
On 31/12/2019 02:08, John Naylor wrote: I'm guessing the initial data for pg_(sh)description is output into separate files because it was too difficult for the traditional shell script to maintain enough state to do otherwise. Yeah, I guess so. The roots of postgres.description goes all the way

remove separate postgres.(sh)description files

2019-12-30 Thread John Naylor
I'm guessing the initial data for pg_(sh)description is output into separate files because it was too difficult for the traditional shell script to maintain enough state to do otherwise. With Perl, it's just as easy to assemble the data into the same format as the rest of the catalogs and then let