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.98.2) (envelope-from ) id 1xCC7l-00000003eEt-15I2 for pgsql-docs@arkaria.postgresql.org; Thu, 01 Oct 2026 08:26:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xCC7k-00000006CcO-1EqK for pgsql-docs@arkaria.postgresql.org; Thu, 01 Oct 2026 08:26:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xCC7k-00000006CcG-05FI for pgsql-docs@lists.postgresql.org; Thu, 01 Oct 2026 08:26:40 +0000 Received: from mail-wm2-x10.google.com ([2a00:1450:4864:31::10]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1xCC7i-00000002AfM-0iN0 for pgsql-docs@lists.postgresql.org; Thu, 01 Oct 2026 08:26:38 +0000 Received: by mail-wm2-x10.google.com with SMTP id 5b1f17b1804b1-49b912d8239so50140515e9.0 for ; Thu, 01 Oct 2026 01:26:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1790843196; x=1791447996; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:content-type :references:in-reply-to:date:to:from:subject:message-id:from:to:cc :subject:date:message-id:reply-to:content-type; bh=fXF2CzonnbpTAzAcz7GJ2JGJtYmA/b64p1YIX5RlW48=; b=ME49bQ8sg+SOCIxkpkuFxcS9mZJ+g4uu5aaC0XzcY5dRQwbYJ65jP1BRL8n0gpX5QW ecCQCWqVMf5oy635gsFlVF+gRckz9Pq+hhv/JW3MZBRcgpMPJIfUOsaBcW+XA2KNsZ/a P8Q+khqMEBv6yixZwyuZXSPK6EeCyUdCJZH+udp5YJENSboWBWd5qGTt8t6EH5E7AJbH J5p5eQwJvynU5Q3ejehQTB7rM3SehX379ndGo/KqnysUTtowlpXa07MnGoBbs+lRy0Z5 ZMOo3LTcxAZyTWyMripj9HiZWSSbKGWCj+GWsuBiEx92tbrJ7IUVgeXWZhk439WyDv/Q mpHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790843196; x=1791447996; h=mime-version:user-agent:content-transfer-encoding:content-type :references:in-reply-to:date:to:from:subject:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=fXF2CzonnbpTAzAcz7GJ2JGJtYmA/b64p1YIX5RlW48=; b=DSuljlVYkBOEJqA6DDlU70h5thIfG3SUZQ3AdGGW3+Rd4Bof4pU1gOeVXc21HvzRps Vh6B0TqwE8NwMEBcvoMGpLEZ8z+V/SAsR8aaGgIGRpdwwtQ3z6bCnj6PE7TRZ9H6WT4Y 2YgZ1CTSrvm+0F9tjgOW2XmZQ/PBO7RTEwowQRptd58s9qiXHyHFljs8K0I4hZPdjT4Y 72xhMNzENqfoTHLbI5RSAyLQh5nbhy5t8ptkmCV3+b+bEE9Wm4J/Qka+sbvEkOTcZYwz asqC9suOZUDdF2KvnKbtyAl86NKMEbTXDNrUe+Eusj8Clq8ukGj4ydM9TXAyN3wJS4s9 LtoA== X-Forwarded-Encrypted: i=1; AKwUvBytq9iy4gHRJgpC4ftHX0Td/Kqy6GTjNjo+4i0dhqExoUTPrBtcOxBcTpPq/fqXDwPN+4KxPGnfsVM8@lists.postgresql.org X-Gm-Message-State: AFuF++lOgMLlKnqYab+fhIjBAtJllbP9XLRwRgLhulyzedmMULX8b4id VR4EqE0U8lmopOy0J0wBnPZSGePbV+qiNuSWnZLZutcKUOYpk2lz5NL8HbBriDF3Zjc= X-Gm-Gg: AYBFou2hgp6/5KUaK40d93infOdYxtXfLCFWhVPakVrSxIAailMJoAm0TGa9hJJ28Wn 5+RzWj9csvUvduvRk0FUEyE546nmETb8MEvt5K/yQkHsRRIc3PaB5T+LYHi18HK0+ap63+Zvxnd 8tLY64yUbjDgZte2t599l6wRki9vdrVz8o1z+WGY6ZQRW8QcTmJAHLiW6AU2iO29cNkTPd4y72Q i2uDUxo67GlgaR6Zf5k/+0yZybjQwWsuP9lCZv4ueUqfz4xKVGpTHGumwcQ4LrDSGw7TlqWepyK HNHcRhiCTBJjZCLfctDInWTPLl5R8Kiud1Yl2kscoHsiElASAheGwvEQoJy2NdEzBe1/ApZAd/Y Xo/3walIGH7YPbd/7EoGsJXndckAd8vcycWHoUpXAp1yROdu+Q5y51Bsa+wXrKYUnWpTHBnRrr6 WECmtFVjN7ZLbUNgtquq4iNz6RTxD1fqaS+KdAa+mftBU8EvPYa6QLHZjmqAn3E34ZpZ4u8lJ7Z o7ThqSRa4m63X8gpjCZgWHkVRaW X-Received: by 2002:a05:600d:82e1:b0:49d:4ef:bf70 with SMTP id 5b1f17b1804b1-4a01addee0emr71064155e9.10.1790843196507; Thu, 01 Oct 2026 01:26:36 -0700 (PDT) Received: from laurenz.albe-K4N0CV00F97414D ([2001:871:70:7db3:6a97:3f66:1df1:4a24]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4a01f984d89sm59732075e9.7.2026.10.01.01.26.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Oct 2026 01:26:35 -0700 (PDT) Message-ID: <62b2bf013e17f856186efb2989c16ff97befc309.camel@cybertec.at> Subject: Re: [Minor] Conflicting sentence in "2.4. Populating a Table With Rows" From: Laurenz Albe To: =?ISO-8859-1?Q?Matem=E1tica?= A3K , "David G. Johnston" , "pgsql-docs@lists.postgresql.org" Date: Thu, 01 Oct 2026 10:26:35 +0200 In-Reply-To: References: <179060786814.1026194.11232417502247566920@wrigleys.postgresql.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.60.2 (3.60.2-2.fc44) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2026-09-29 at 15:00 -0300, Matem=C3=A1tica A3K wrote: > > > Yeah, that last part could use some cleanup.=C2=A0 I=E2=80=99d probab= ly rewrite it using csv though instead of tab-delimited so as to remove the= need for a parenthetical. > > >=20 > > > David J. > =C2=A0 > I'm attaching the patch although without the format that Laurenz used (no= t sure if it is needed though). >=20 > It fixes the problem and removes the parenthetical, do you think is OK? No issue with the format of the patch, but with the content. The COPY statement uses the default tab-separated TEXT format, so your CSV = data wouldn't work with it. The wording in the documentation is confusing, because it does not indicate that the file below belongs to the COPY statement above. I think this should read: You could also have used COPY to load large amounts of data from flat-tex= t files. [...] An example would be: COPY weather FROM '/home/user/weather.txt'; where the file name for the source file must be available on the machine = running the backend process, not the client, since the backend process reads the file= directly. The file used in the COPY statement above could look a= s follows (the values are separated by a tab character): San Francisco 46 50 0.25 1994-11-27 San Francisco 43 57 0.0 1994-11-29 Hayward 37 54 \N 1994-11-29 Yours, Laurenz Albe