| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | bchen90(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18112: pgstattuple of sequence failed |
| Date: | 2023-09-20 08:26:07 |
| Message-ID: | 202309200826.z3ckjb4g7auj@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2023-Sep-15, PG Bug reporting form wrote:
> I found pgstattuple of sequence will be failed but not PG11.x, for the code
> of pgstattuple it looks like still support of sequence, but the
> "rel->rd_rel->relam now is 0, not HEAP_TABLE_AM_OID", so the error report
>
> postgres=# select pgstattuple('test');
> ERROR: SQLSTATE 0A000: only heap AM is supported
OK, but so what? I mean, what useful information are you extracting
using pgstattuple from a sequence? What decisions can you make based on
these results?
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"We're here to devour each other alive" (Hobbes)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-09-20 09:08:31 | BUG #18117: View definitions were changed in version 16 (missing column qualifiers) |
| Previous Message | daidewei@highgo.com | 2023-09-20 06:34:06 | Re: Re: a plpgsql bug |