| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Kazutaka Onishi <onishi(at)heterodb(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Kohei KaiGai <kaigai(at)heterodb(dot)com> |
| Subject: | Re: TRUNCATE on foreign table |
| Date: | 2021-02-11 13:23:24 |
| Message-ID: | CAExHW5tceUdJSYMy6R8uYzJ2upKfKdJdWPyUmM16-_xEdFGL0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 10, 2021 at 10:58 PM Kazutaka Onishi <onishi(at)heterodb(dot)com> wrote:
>
> That's because using the foreign server is difficult for the user.
>
> For example, the user doesn't always have the permission to login to the forein server.
> In some cases, the foreign table has been created by the administrator that has permission to access the two servers and the user only uses the local server.
> Then the user has to ask the administrator to run TRUNCATE every time.
That might actually be seen as a loophole but ...
>
> Furthermore,there are some fdw extensions which don't support SQL. mongo_fdw, redis_fdw, etc...
> These extensions have been used to provide SQL interfaces to the users.
> It's hard for the user to run TRUNCATE after learning each database.
this has some appeal.
Thanks for sharing the usecases.
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2021-02-11 13:24:28 | Re: Transactions involving multiple postgres foreign servers, take 2 |
| Previous Message | Peter Eisentraut | 2021-02-11 13:23:14 | Add tests for bytea LIKE operator |