pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedNeed clarification on "field"
3+ messages / 3 participants
[nested] [flat]
* Need clarification on "field"
@ 2024-06-04 19:54 PG Doc comments form <noreply@postgresql.org>
2024-06-05 10:15 ` Re: Need clarification on "field" Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2024-06-04 19:54 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: boopalan_sjb@yahoo.co.in
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/limits.html
Description:
Under page "https://www.postgresql.org/docs/current/limits.html";, below
limitations are mentioned:
field size - 1 GB
identifier length - 63 bytes
I understand "identifier" as the name we provide for tables, columns etc.
By the way, what is "field" in Postgresql? I don't see any official
page/explanation for this.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Need clarification on "field"
2024-06-04 19:54 Need clarification on "field" PG Doc comments form <noreply@postgresql.org>
@ 2024-06-05 10:15 ` Laurenz Albe <laurenz.albe@cybertec.at>
2024-06-05 14:07 ` Re: Need clarification on "field" Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 3+ messages in thread
From: Laurenz Albe @ 2024-06-05 10:15 UTC (permalink / raw)
To: boopalan_sjb@yahoo.co.in; pgsql-docs@lists.postgresql.org
On Tue, 2024-06-04 at 19:54 +0000, PG Doc comments form wrote:
> Under page "https://www.postgresql.org/docs/current/limits.html";, below
> limitations are mentioned:
>
> field size - 1 GB
> identifier length - 63 bytes
>
> I understand "identifier" as the name we provide for tables, columns etc.
>
> By the way, what is "field" in Postgresql? I don't see any official
> page/explanation for this.
The PostgreSQL term would be "attribute". Perhaps we should use that.
Alternatively, what about "column value"? It is perhaps not accurate,
because a Datum need not be stored in a column, but it might be readily
understandable.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Need clarification on "field"
2024-06-04 19:54 Need clarification on "field" PG Doc comments form <noreply@postgresql.org>
2024-06-05 10:15 ` Re: Need clarification on "field" Laurenz Albe <laurenz.albe@cybertec.at>
@ 2024-06-05 14:07 ` Bruce Momjian <bruce@momjian.us>
0 siblings, 0 replies; 3+ messages in thread
From: Bruce Momjian @ 2024-06-05 14:07 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: boopalan_sjb@yahoo.co.in; pgsql-docs@lists.postgresql.org
On Wed, Jun 5, 2024 at 12:15:45PM +0200, Laurenz Albe wrote:
> On Tue, 2024-06-04 at 19:54 +0000, PG Doc comments form wrote:
> > Under page "https://www.postgresql.org/docs/current/limits.html";, below
> > limitations are mentioned:
> >
> > field size - 1 GB
> > identifier length - 63 bytes
> >
> > I understand "identifier" as the name we provide for tables, columns etc.
> >
> > By the way, what is "field" in Postgresql? I don't see any official
> > page/explanation for this.
>
> The PostgreSQL term would be "attribute". Perhaps we should use that.
> Alternatively, what about "column value"? It is perhaps not accurate,
> because a Datum need not be stored in a column, but it might be readily
> understandable.
The way I understand it, we have rows and columns, and each "cell" is a
field.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2024-06-05 14:07 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-06-04 19:54 Need clarification on "field" PG Doc comments form <noreply@postgresql.org>
2024-06-05 10:15 ` Laurenz Albe <laurenz.albe@cybertec.at>
2024-06-05 14:07 ` Bruce Momjian <bruce@momjian.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox