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 1sJxy0-007cJA-F9 for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 16:15:24 +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 1sJxxy-0022LZ-1F for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 16:15:22 +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.94.2) (envelope-from ) id 1sJxxx-0022LR-Kc for pgsql-general@lists.postgresql.org; Wed, 19 Jun 2024 16:15:22 +0000 Received: from mail-oo1-xc29.google.com ([2607:f8b0:4864:20::c29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJxxv-0026QP-Ri for pgsql-general@lists.postgresql.org; Wed, 19 Jun 2024 16:15:21 +0000 Received: by mail-oo1-xc29.google.com with SMTP id 006d021491bc7-5b97539a4a5so3704430eaf.2 for ; Wed, 19 Jun 2024 09:15:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718813719; x=1719418519; 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=xkQAt4fndKyr875kxP9MYZFmMPYHpjw8lDoEhasdjxc=; b=UDT3NSuLAl8sV9ZIbiOiBsbNUMNYm68YEfvCiG5CwaWfbsTQ/e+HW07LFAW1rpTRsj 3wF9qaFS5TYoAPYqoPrDFVEIzLPSk9mNTCYD/FlQ+i6H+JYjTuybm3rBRKJ42Hy3j68X +xRBoTejE/aCWSxN5gTds5NaijDw2DIXdYAYhaO9iXfn5h6Ixr0Vs7wYm5XlZt95ghu/ 2vLxBTgUetglkwW5i+3jS8bBiY53C4cXuhs+giiB/JXIC9n05q+Yf6s6R6n9LVQLBhUe 6lE5/eeCy2C1K0++6kVc4hW1grTPbDiKCtFgSUVKoZKQqqEdM3ZF9ZkrJREFECPKD08T E7qQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718813719; x=1719418519; 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=xkQAt4fndKyr875kxP9MYZFmMPYHpjw8lDoEhasdjxc=; b=aQoNM8A8X2KzamfO4Xrich0UYdZKkZpM0yVXS8fJKbBd/XOQVoTGSAmYuYSwqzBg/i YCkeDvZD9L/60yqoxkfZEC4NsccgqXVV4xQ/lszjcX+s20ufEK262iZ1BFT1/tQGX9HB wcxt+JoImto6Wjt12/fxpKiDRvOyPdWIHspArCKqjcGIKuEdT7H7hV2Mp1ndO5NnGjjt cbuINypK15aCE2d9YSsQT5pZFYUrbmkLdaKE4RqqGsUwRbK0b9/DLQCb1W00ZJDMSD4n HYqmshFpr4Cu6VHbMUmgCCUB7snqotpMOlRwZznOiHwAgvhucx3BaVzdd4I5AyeDHtAl D8og== X-Gm-Message-State: AOJu0YxE2yPshX8iHmBMjcVYvItRrjO2FLpy8U/p00T20B1PawGPgv9k aAg8TLSg0L4pVVMPB81O7DD+gTxJrbojc7w3rBeNDozPQgtPUDvHyU9d8qGJOT44geaGcinR4X+ 82vd6Et/8iLYkH31jZu5vUI1wWK2aWQ== X-Google-Smtp-Source: AGHT+IHMZDfc2CFB7sLnNWSvymdpCDnwYDLhwQVxNn+ZXSy0mQ8ggpUkn6DDcWn5GZsG6dLBtxAi0khyEnJqa5haPLs= X-Received: by 2002:a05:6870:d112:b0:254:b5b9:354e with SMTP id 586e51a60fabf-25c94990accmr3586221fac.19.1718813719103; Wed, 19 Jun 2024 09:15:19 -0700 (PDT) MIME-Version: 1.0 References: <9f2bfd4-1c20-ea61-40c1-b9911f6049b@appl-ecosys.com> In-Reply-To: <9f2bfd4-1c20-ea61-40c1-b9911f6049b@appl-ecosys.com> From: "David G. Johnston" Date: Wed, 19 Jun 2024 09:14:41 -0700 Message-ID: Subject: Re: Proper format for pg_dump file date To: Rich Shepard Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000298e72061b408173" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000298e72061b408173 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 19, 2024 at 8:55=E2=80=AFAM Rich Shepard wrote: > Is the correct date format for pg_dump > -$(date +%Y-%m-%d).sql > or > -YYYY-MM-DD.sql > or something else? > > 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 those are generally best avoided. David J. --000000000000298e72061b408173 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jun 19, 2024 at 8:55=E2=80=AFAM Rich Shepard <<= a href=3D"mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com>= wrote:
Is the correct date format for pg_dump
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <filename>-$(date +%Y-%m-%d).sql
or
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <filename>-YYYY-MM-DD.sql
or something else?


If you are doing a= custom format dump using .sql as the extension is objectively wrong.=C2=A0= it is correct if you are doing an sql dump, but those are generally best a= voided.

David J.
--000000000000298e72061b408173--