| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: behave of --create-slot option |
| Date: | 2018-06-01 02:59:04 |
| Message-ID: | CA+TgmobyfB5YKEk3un9gkCEo+o7hJeM8Y+0EfdwhHjN4oV_wMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg스포츠 토토 사이트SQL |
On Wed, May 30, 2018 at 2:00 PM, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Hm. There could be an argument for improving the user experience here
> so as some cleanup is at least attempted except if --no-clean is defined
> by the caller when --create-slot is used. Do we want an open item for
> this issue?
Sounds like new development to me. This isn't a bug.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2018-06-01 03:00:36 | Re: I'd like to discuss scaleout at PGCon |
| Previous Message | Andrew Gierth | 2018-06-01 02:16:53 | Re: json results parsing |