MIME-Version: 1.0
References: <9f2bfd4-1c20-ea61-40c1-b9911f6049b@appl-ecosys.com>
 <CAKFQuwZO_J+LhHK6iL_AB2FzFickN=Z8ELb4T5spivatoUpTjQ@mail.gmail.com> <6866ca28-7cba-df1f-7315-1317a1441766@appl-ecosys.com>
In-Reply-To: <6866ca28-7cba-df1f-7315-1317a1441766@appl-ecosys.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Wed, 19 Jun 2024 13:17:40 -0400
Message-ID: <CANzqJaBODFMzxXMP=PwEVdW4hASGKfxa1r8iKiYbC4Q-3tnn5g@mail.gmail.com>
Subject: Re: Proper format for pg_dump file date
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000c9f19d061b4160fa"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaBODFMzxXMP%3DPwEVdW4hASGKfxa1r8iKiYbC4Q-3tnn5g%40mail.gmail.com>
Precedence: bulk

--000000000000c9f19d061b4160fa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 19, 2024 at 1:14=E2=80=AFPM Rich Shepard <rshepard@appl-ecosys.=
com>
wrote:

> On Wed, 19 Jun 2024, David G. Johnston wrote:
>
> > If you are doing a custom format dump using .sql as the extension is
> > objectively wrong. it is correct if you are doing an sql dump, but thos=
e
> > are generally best avoided.
>
> David,
>
> I use the default text format so restoration is by psql.
>

Perfectly valid for small databases, and copying tables from one instance
to another (though in that case, consider postgres_fdw).

--000000000000c9f19d061b4160fa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jun 19, 2024 at 1:14=E2=80=AFPM R=
ich Shepard &lt;<a href=3D"mailto:rshepard@appl-ecosys.com">rshepard@appl-e=
cosys.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">On Wed, 19 Jun 2024, David G. Johnston =
wrote:<br>
<br>
&gt; If you are doing a custom format dump using .sql as the extension is<b=
r>
&gt; objectively wrong. it is correct if you are doing an sql dump, but tho=
se<br>
&gt; are generally best avoided.<br>
<br>
David,<br>
<br>
I use the default text format so restoration is by psql.<br>
</blockquote><div><br></div><div>Perfectly valid for small databases, and c=
opying tables from one instance to another (though in that case, consider p=
ostgres_fdw).</div><div><br></div></div></div>

--000000000000c9f19d061b4160fa--