| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt |
| Date: | 2025-08-22 15:50:52 |
| Message-ID: | 1885537.1755877852@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)de> writes:
> Yeah, AFAIR I wrote it (or at least heavily edited the original to get
> to that), and I was trying to convey exactly those two ideas. If you
> want to propose improvements, they're very welcome.
Hmmm ... maybe something like
Mathematically, a "relation" is a set of tuples; this is the sense
meant in the term "relational database".
In Postgres, "relation" is commonly used to mean a database object
that has a name and a list of attributes defined in a specific
order. Tables, sequences, views, foreign tables, materialized
views, composite types, and indexes are all relations. A relation
in this sense is a container or descriptor for a set of tuples.
"Class" is an alternative but archaic term. The system catalog
pg_class holds an entry for each Postgres relation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-08-22 16:14:24 | Re: Don't treat virtual generated columns as missing statistics in vacuumdb --missing-stats-only |
| Previous Message | shveta malik | 2025-08-22 15:49:44 | Re: Conflict detection for update_deleted in logical replication |