Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rzdtI-005YK1-Oj for pgsql-hackers@arkaria.postgresql.org; Wed, 24 Apr 2024 14:46:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rzdtF-00FcTr-DP for pgsql-hackers@arkaria.postgresql.org; Wed, 24 Apr 2024 14:46:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rzdtF-00FcTj-3t for pgsql-hackers@lists.postgresql.org; Wed, 24 Apr 2024 14:46:29 +0000 Received: from mail-ot1-x32f.google.com ([2607:f8b0:4864:20::32f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rzdtC-002ihp-G7 for pgsql-hackers@lists.postgresql.org; Wed, 24 Apr 2024 14:46:28 +0000 Received: by mail-ot1-x32f.google.com with SMTP id 46e09a7af769-6ed06982819so2511993a34.0 for ; Wed, 24 Apr 2024 07:46:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713969984; x=1714574784; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=B3X+k6IDjFuAR3lpPuhd5H5E7GhpHgFClYYqNsR3B8k=; b=eeIssppLo6fmhFkcCwulQW0E4REkFToTngR4HlJ9JXU14QitvPftJ1pwFfKV7/Ko4H GbcnqWl5y6VLF0+TfcciBNnoBqsb7eD/FbEI8r4sI/Vh74yZRpC5XVC4FjkBGfvuuhsZ C9kqeQaehhNCmbAbEcIb1tkQiOi2TCv0EAZsKEqqAX0qqr87/mjW/EBPGnNku6d69HPG cYgC6qTuqY0hbobdQMWHkOTUDIkQ80nDo5q9jggYoOZBVpCRnnIFCFx2OqJB7TpvpZ8R bacefAJp++mTpS6CMO5YZcTYXlSZdSOMeYX+A36jsNHBXqv7j/tYn/v1xNyu/2fKPTnT gwWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713969984; x=1714574784; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=B3X+k6IDjFuAR3lpPuhd5H5E7GhpHgFClYYqNsR3B8k=; b=IDXbWIqi/aQtHgKz/jK5iiSepasjkJTNta6NOODDMeMozcVm15AEXZwTPvB8pihTU8 uLzXFfikVjHOeae1ZJKZX1NjqYMMmhClewgcLFPcfmd42XdD0GUX851CxycVBVZGPaC+ Wdp/+9cjN/mwU8SM4EN80wYVzERC5Cn6f4hArg01zO7l30C3bXYixnOcJ4Pp/3KYs3z5 btAY2QvVa791vFgj3BWrLCZAGHZHyXEPIaTdbm8d1F8jSccpy1JLc2MZD9hk9mobZmb7 JaZxEhKcLS0jhPQk0FiykphYA26Y7b3DwfZycqVMxbyu2NSwMPCgqniVgEIBJxjJMZ+E ucpw== X-Gm-Message-State: AOJu0YwprUdBFaOW/NsjtQsB8HN23Qrb9MQhCkurRD8bf1cdGb79sDQ8 IUjlA7IKQWYI249wopCPHS5R1CluwoC1XHhRKJdWnXU1p0CQ8/ZA2OOowwEX74icM9/YfwrGS0s ArVYEE90Gk2A0kE1t9Z8MIcuEO1OaGQ== X-Google-Smtp-Source: AGHT+IGirNRXCyFD453YkBS8hbYfpQhImL3EjUoJRMOJsrUQYflEC5nQxM8JdmKCuHeFbSdgsMqMozXXtlcLVIa0x7A= X-Received: by 2002:a05:6871:8a2:b0:22e:76c1:ddce with SMTP id r34-20020a05687108a200b0022e76c1ddcemr2840001oaq.6.1713969984453; Wed, 24 Apr 2024 07:46:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Wed, 24 Apr 2024 07:45:47 -0700 Message-ID: Subject: Re: doc: create table improvements To: Peter Eisentraut Cc: PostgreSQL Hackers Content-Type: multipart/alternative; boundary="00000000000014454b0616d8bc76" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000014454b0616d8bc76 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Apr 24, 2024 at 3:30=E2=80=AFAM Peter Eisentraut wrote: > > + The reliability characteristics of a table are governed by its > > + persistence mode. The default mode is described > > + here > > + There are two alternative modes that can be specified during > > + table creation: > > + temporary and > > + unlogged. > > Not sure reliability is the best word here. I mean, a temporary table > isn't any less reliable than any other table. It just does different > things. > > Given the name of the section where this is all discussed I'm having trouble going with a different word. But better framing and phrasing I can do: A table may be opted out of certain storage aspects of reliability, as described [here], by specifying either of the alternate persistence modes: [temporary] or [logged]. The specific trade-offs and implications are detailed below. David J. --00000000000014454b0616d8bc76 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Apr 24, 2024 at 3:30=E2=80=AFAM Peter Eisentraut &= lt;peter@eisentraut.org> wro= te:
=C2=A0> +=C2=A0 =C2=A0The reliability charac= teristics of a table are governed by its
=C2=A0> +=C2=A0 =C2=A0persistence mode.=C2=A0 The default mode is descri= bed
=C2=A0> +=C2=A0 =C2=A0<link linkend=3D"wal-reliability">= here</link>
=C2=A0> +=C2=A0 =C2=A0There are two alternative modes that can be specif= ied during
=C2=A0> +=C2=A0 =C2=A0table creation:
=C2=A0> +=C2=A0 =C2=A0<link linkend=3D"sql-createtable-temporary= ">temporary</link> and
=C2=A0> +=C2=A0 =C2=A0<link linkend=3D"sql-createtable-unlogged&= quot;>unlogged</link>.

Not sure reliability is the best word here.=C2=A0 I mean, a temporary table=
isn't any less reliable than any other table.=C2=A0 It just does differ= ent
things.


Given the name of the section where this= is all discussed I'm having trouble going=C2=A0with a different word.= =C2=A0 But better framing and phrasing I can do:

A tab= le may be opted out of certain storage aspects of reliability, as described= [here], by specifying either of the alternate persistence modes: [temporar= y] or [logged]. The specific trade-offs and implications are detailed below= .

David J.

--00000000000014454b0616d8bc76--