| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fallback table AM for relkinds without storage |
| Date: | 2021-03-14 11:59:08 |
| Message-ID: | YE36jH2KFqAnTm9a@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 24, 2021 at 11:51:36AM +0900, Michael Paquier wrote:
> For the file name, using something like pseudo_handler.c or similar
> would be fine, I guess. However, if we go down the path of one AM per
> relkind for the slot callback, then why not just calling the AMs
> foreign_table_am, view_am and part_table_am? This could be coupled
> with sanity checks to make sure that AMs assigned to those relations
> are the expected ones.
I am still not quite sure what needs to be done here and this needs
more thoughts, so this has been marked as returned with feedback for
now. Instead of pushing forward with this patch, I'll just spend more
cycles on stuff that has more chances to make it into 14.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2021-03-14 12:14:49 | Re: Using COPY FREEZE in pgbench |
| Previous Message | Michael Paquier | 2021-03-14 11:54:11 | Re: REINDEX backend filtering |