| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | mail(at)joeconway(dot)com, pavel(dot)stehule(at)gmail(dot)com, myon(at)debian(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, andres(at)anarazel(dot)de, andreas(at)proxel(dot)se, tomas(dot)vondra(at)2ndquadrant(dot)com, eldmannen(at)gmail(dot)com, mark(dot)kirkwood(at)catalyst(dot)net(dot)nz, michael(at)paquier(dot)xyz, chris(dot)travers(at)adjust(dot)com, alvherre(at)2ndquadrant(dot)com, euler(at)timbira(dot)com(dot)br, rjuju123(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL pollutes the file system |
| Date: | 2019-04-10 19:45:52 |
| Message-ID: | e6e1c596-b544-8e3b-443f-e8bdf9a2d7ff@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-pkg-debian |
On 2019-04-10 15:01, Tatsuo Ishii wrote:
>> On 2019-03-29 20:32, Joe Conway wrote:
>>> pg_util <command> <options>
>>
>> How is that better than just renaming to pg_$oldname?
>
> As I already said in up thread:
>
>> This way, we would be free from the command name conflict problem
Well, whatever we do -- if anything -- we would certainly need to keep
the old names around for a while somehow. So this doesn't really make
that issue go away.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2019-04-10 19:57:38 | Re: block-level incremental backup |
| Previous Message | Peter Eisentraut | 2019-04-10 19:44:28 | Re: PostgreSQL pollutes the file system |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Isaac Morland | 2019-04-10 21:08:16 | Re: PostgreSQL pollutes the file system |
| Previous Message | Peter Eisentraut | 2019-04-10 19:44:28 | Re: PostgreSQL pollutes the file system |