| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Pluggable Storage - Andres's take |
| Date: | 2018-12-17 15:18:20 |
| Message-ID: | CA+q6zcVc+OSC8R3gHNzExbY1pSnuOwh-mXBGvaR5dFaxRX44+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Sat, Dec 15, 2018 at 8:37 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> We need to dump the table access method at dump time, otherwise we loose
> that information.
Oh, right. So, something like in the attached patch?
> > As a side note, in a table description I haven't found any mention of which
> > access method is used for this table, probably it's useful to show that with \d+
> > (see the attached patch).
>
> I'm not convinced that's really worth the cost of including it in \d
> (rather than \d+ or such).
Maybe I'm missing the point, but I've meant exactly the same and the patch,
suggested in the previous email, add this info to \d+
| Attachment | Content-Type | Size |
|---|---|---|
| pg_dump_access_method.patch | application/octet-stream | 3.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2018-12-17 15:58:03 | Re: [HACKERS] WIP: Aggregation push-down |
| Previous Message | Amit Langote | 2018-12-17 14:57:09 | Re: slight tweaks to documentation about runtime pruning |