Re: [HACKERS] postgres_fdw : altering foreign table not invalidatingprepare statement execution plan.
| От | Ashutosh Bapat |
|---|---|
| Тема | Re: [HACKERS] postgres_fdw : altering foreign table not invalidatingprepare statement execution plan. |
| Дата | |
| Msg-id | CAFjFpRdY5q1HG1N4eyrZxHYji4HS1X4TAGDEKUQXv9h3YomcrQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] postgres_fdw : altering foreign table not invalidatingprepare statement execution plan. (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>) |
| Ответы |
Re: [HACKERS] postgres_fdw : altering foreign table not invalidatingprepare statement execution plan.
|
| Список | pgsql-hackers |
On Thu, Jan 5, 2017 at 2:49 PM, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote: > On 2017/01/03 15:57, Ashutosh Bapat wrote: >> >> The patch looks good to me, but I feel there are too many testscases. >> Now that we have changed the approach to invalidate caches in all >> cases, should we just include cases for SELECT or UPDATE or INSERT or >> DELETE instead of each statement? > > > I don't object to that, but (1) the tests I added wouldn't be that > time-consuming, and (2) they would be more expected to help find bugs, in > general, so I'd vote for keeping them. How about leaving that for the > committer's judge? > Ok. Marking this as ready for committer. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
В списке pgsql-hackers по дате отправления: