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 1tUtO3-003c9F-0p for pgsql-admin@arkaria.postgresql.org; Mon, 06 Jan 2025 20:07:43 +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 1tUtO2-00CEMP-CP for pgsql-admin@arkaria.postgresql.org; Mon, 06 Jan 2025 20:07:42 +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 1tUtO1-00CEMH-Vu for pgsql-admin@lists.postgresql.org; Mon, 06 Jan 2025 20:07:41 +0000 Received: from mail-vk1-xa35.google.com ([2607:f8b0:4864:20::a35]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tUtNy-000DVc-2u for pgsql-admin@lists.postgresql.org; Mon, 06 Jan 2025 20:07:41 +0000 Received: by mail-vk1-xa35.google.com with SMTP id 71dfb90a1353d-51889930cb1so4346584e0c.0 for ; Mon, 06 Jan 2025 12:07:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736194057; x=1736798857; 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=170nCk5yqI+8Bd3uU30dOtxWWO7ERz4W+4NSZVZNCQE=; b=j0b+jjX2rgIyPATIwoWh3lcrvYRoJFKkLsYS6//BwOKjXH28/WHgeqGCGUwhjL3Lij zLaXFMjCGZogNr4J+ZC/vCyVZj3GRDSb0488+DZUyZgCaYDaECCl5QmthLIFMPjT1L1X OSqOWVFfyYV0iEvNAfGvPk7xZjS2WsREpkhqC4ZpBBtGPj1DfS6d64NwPouc5VOghOcO ZdYQcjEd2//SeQr4o0ReJoAPO0GDZlosdsMxh+EXE5c6lBsO4UNsNLrScVhq1TSKHHwk JwG0f0L4xthYerDmYQyjgeuHVKQTez2wIuyzB18g4k5hohGJdjuSj7oeV093MkMykyK8 Pk3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736194057; x=1736798857; 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=170nCk5yqI+8Bd3uU30dOtxWWO7ERz4W+4NSZVZNCQE=; b=e/3OsFWMcvvhz87sbb3aXYT+EdXVrxUEpW1Q+tuYYj1y92p1j0GMnPaOZXjkbL56OA 3YM+3LmyYbj/HVGSDmoY2xAdkfh2JhjahenBsz9ASMSmZ9PNcqpv1rfqRJfZjMhhYnW6 EbZbQq046GlgNS9AfWY+OXNP2xLC5QE6FBwQvhf+AZX6/7aJ/5gRgYeB1rYc/8cdSsz/ wlwyL/sFTIGcOjwAZ1QyqsC14GmQDBu56C8AYx+Gn7/7xE5iE78+bLn5QV2jU8bYvYuv IwcewOE3UZ/VfMi5rPOVoNOrfX1dw9Ksj2kt6gG9fR1bCnYC7XMwESaC7S2HMhLuBNMB AzQA== X-Gm-Message-State: AOJu0Yy/J8YNp+4IzJMGCKrHkqjj68yJfonlIt+dihBpPlCLruLVWodt XPnIJDgAt7XMjhlleI8f/Gnkchuq35sdVZ6PXonH/BwU8uIQtE3fuEZxMqQi311aGDAMeMlnryJ XrAD4zAHY6RJDF76EexkH/KCP8tghLtYa X-Gm-Gg: ASbGncsF640v/fCi+MIaTzMw2NOWmIAtoO6l4bNDm+/D8K5aQlPK/wO+rYBFYFJSo+j 4kk7e1xFU52FDySbCEYJ3gntujETKG4g5gY/uGdG+DWkoefCaw3rybgeJ0qLYeLUvnOE= X-Google-Smtp-Source: AGHT+IEUZgw4UPp38Y9bRQEVKkq1EmJmBut0CKjUBcpI/+JiHQ95p5eFlZlofri15fzqobUJ8z4llVqBnJB91y+AMXk= X-Received: by 2002:a05:6122:1b0b:b0:515:5008:118b with SMTP id 71dfb90a1353d-51b75c42de6mr40917178e0c.1.1736194057406; Mon, 06 Jan 2025 12:07:37 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Mauricio Fernandez Date: Mon, 6 Jan 2025 17:07:26 -0300 X-Gm-Features: AbW1kvYCuxuWFzy_MC92u82R96YHi6M9UvpBW0XNEdk3JBL4xyqv9ytWNxMUZls Message-ID: Subject: Re: Postgresql 17 incremental backup To: Guillaume Lelarge Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="0000000000000d9287062b0f2eec" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000d9287062b0f2eec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ups, thanks for the warning Hi Guillaume, thanks for the answer. I've tried with -i and --incremental , and the results are the same. In both cases without "=3D" [postgres@buda viernes]$ pg_basebackup -c fast -P -D /var/lib/pgsql/17/backups/devadv01/fisicos/viernes =E2=80=93-incremental /var/lib/pgsql/17/backups/devadv01/fisicos/base_plano/backup_manifest pg_basebackup: error: demasiados argumentos en la l=C3=ADnea de =C3=B3rdene= s (el primero es =C2=AB=E2=80=93-incremental=C2=BB) pg_basebackup: consejo: Pruebe =C2=ABpg_basebackup --help=C2=BB para mayor informaci=C3=B3n. [postgres@buda viernes]$ pg_basebackup -c fast -P -D /var/lib/pgsql/17/backups/devadv01/fisicos/viernes =E2=80=93i /var/lib/pgsql/17/backups/devadv01/fisicos/base_plano/backup_manifest pg_basebackup: error: demasiados argumentos en la l=C3=ADnea de =C3=B3rdene= s (el primero es =C2=AB=E2=80=93i=C2=BB) pg_basebackup: consejo: Pruebe =C2=ABpg_basebackup --help=C2=BB para mayor informaci=C3=B3n. regards MF El lun, 6 ene 2025 a las 17:01, Guillaume Lelarge (= ) escribi=C3=B3: > Hi, > > Reply to the list, not only to me. > > Le lun. 6 janv. 2025 =C3=A0 20:52, Mauricio Fernandez < > mmauricio.fernandez@gmail.com> a =C3=A9crit : > >> Hi Guillaume, thanks for the answer. >> >> I've tried with -i and --incremental , and the results are the same. In >> both cases without "=3D" >> >> [postgres@buda viernes]$ pg_basebackup -c fast -P -D >> /var/lib/pgsql/17/backups/devadv01/fisicos/viernes =E2=80=93-incremental >> /var/lib/pgsql/17/backups/devadv01/fisicos/base_plano/backup_manifest >> >> pg_basebackup: error: demasiados argumentos en la l=C3=ADnea de =C3=B3rd= enes (el >> primero es =C2=AB=E2=80=93-incremental=C2=BB) >> pg_basebackup: consejo: Pruebe =C2=ABpg_basebackup --help=C2=BB para may= or >> informaci=C3=B3n. >> >> [postgres@buda viernes]$ pg_basebackup -c fast -P -D >> /var/lib/pgsql/17/backups/devadv01/fisicos/viernes =E2=80=93i >> /var/lib/pgsql/17/backups/devadv01/fisicos/base_plano/backup_manifest >> pg_basebackup: error: demasiados argumentos en la l=C3=ADnea de =C3=B3rd= enes (el >> primero es =C2=AB=E2=80=93i=C2=BB) >> pg_basebackup: consejo: Pruebe =C2=ABpg_basebackup --help=C2=BB para may= or >> informaci=C3=B3n. >> >> > I've tried your command line, and I have the same error. The minus sign i= s > not the good one. Try: > > pg_basebackup -c fast -P -D > /var/lib/pgsql/17/backups/devadv01/fisicos/viernes --incremental > /var/lib/pgsql/17/backups/devadv01/fisicos/base_plano/backup_manifest > > > >> regards >> >> MF >> >> >> El lun, 6 ene 2025 a las 16:42, Guillaume Lelarge (< >> guillaume@lelarge.info>) escribi=C3=B3: >> >>> Hi, >>> >>> Le lun. 6 janv. 2025 =C3=A0 20:23, Mauricio Fernandez < >>> mmauricio.fernandez@gmail.com> a =C3=A9crit : >>> >>>> Hi admins, I'm trying to execute an incremental backup and I'm getting >>>> the following error >>>> >>>> *[postgres@buda ~]$ pg_basebackup -c fast -P -D $PGBKP/fisicos/viernes >>>> =E2=80=93-incremental=3D$PGBKP/fisicos/base_plano/backup_manifest* >>>> pg_basebackup: error: demasiados argumentos en la l=C3=ADnea de =C3=B3= rdenes (el >>>> primero es >>>> =C2=AB=E2=80=93-incremental=3D/var/lib/pgsql/17/backups/devadv01/fisic= os/base_tar/backup_manifest=C2=BB) >>>> pg_basebackup: consejo: Pruebe =C2=ABpg_basebackup --help=C2=BB para m= ayor >>>> informaci=C3=B3n. >>>> >>>> *The literal translation of the error message is: pg_basebackup: error= : >>>> too many arguments in the command line (the first is >>>> =C2=AB=E2=80=93-incremental=3D/var/lib/pgsql/17/backups/devadv01/fisic= os/base_tar/backup_manifest=C2=BB)* >>>> >>>> >>> It looks like it thinks that >>> "--incremental=3D/var/lib/pgsql/17/backups/devadv01/fisicos/base_tar/ba= ckup_manifest" >>> is one argument rather than an argument and its value. Try getting rid = of >>> the equal value. Maybe it will help. >>> >>> >>> -- >>> Guillaume. >>> >> > > -- > Guillaume. > --0000000000000d9287062b0f2eec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ups, thanks for the warning

Hi Guillaum= e, thanks for the answer.

I've tried with -i and --i= ncremental , and the results are the same. In both cases without "=3D&= quot;=C2=A0=C2=A0

[postgres@buda viernes]$ pg_basebackup = -c fast -P -D /var/lib/pgsql/17/backups/devadv01/fisicos/viernes =E2=80=93-= incremental =C2=A0/var/lib/pgsql/17/backups/devadv01/fisicos/base_plano/bac= kup_manifest

pg_basebackup: error: demasiados argume= ntos en la l=C3=ADnea de =C3=B3rdenes (el primero es =C2=AB=E2=80=93-increm= ental=C2=BB)
pg_basebackup: consejo: Pruebe =C2=ABpg_basebackup --help= =C2=BB para mayor informaci=C3=B3n.

[postgres@buda viernes]$ pg_base= backup -c fast -P -D /var/lib/pgsql/17/backups/devadv01/fisicos/viernes =E2= =80=93i /var/lib/pgsql/17/backups/devadv01/fisicos/base_plano/backup_manife= st
pg_basebackup: error: demasiados argumentos en la l=C3=ADnea de =C3= =B3rdenes (el primero es =C2=AB=E2=80=93i=C2=BB)
pg_basebackup: consejo:= Pruebe =C2=ABpg_basebackup --help=C2=BB para mayor informaci=C3=B3n.

regards

MF

El lun, 6 ene 2025 a las 17:01, Guillaume Lelarge (<guillaume@lelarge.info>) e= scribi=C3=B3:
Hi,

Reply to = the list, not only to me.

Le=C2=A0lun. 6 janv. 2025 =C3=A0=C2=A020= :52, Mauricio Fernandez <mmauricio.fernandez@gmail.com> a =C3=A9crit=C2= =A0:
Hi Guillaume, thanks for the answer.

I've trie= d with -i and --incremental , and the results are the same. In both cases w= ithout "=3D"=C2=A0=C2=A0

[postgres@buda viernes= ]$ pg_basebackup -c fast -P -D /var/lib/pgsql/17/backups/devadv01/fisicos/v= iernes =E2=80=93-incremental =C2=A0/var/lib/pgsql/17/backups/devadv01/fisic= os/base_plano/backup_manifest

pg_basebackup: error: = demasiados argumentos en la l=C3=ADnea de =C3=B3rdenes (el primero es =C2= =AB=E2=80=93-incremental=C2=BB)
pg_basebackup: consejo: Pruebe =C2=ABpg_= basebackup --help=C2=BB para mayor informaci=C3=B3n.

[postgres@buda = viernes]$ pg_basebackup -c fast -P -D /var/lib/pgsql/17/backups/devadv01/fi= sicos/viernes =E2=80=93i /var/lib/pgsql/17/backups/devadv01/fisicos/base_pl= ano/backup_manifest
pg_basebackup: error: demasiados argumentos en la l= =C3=ADnea de =C3=B3rdenes (el primero es =C2=AB=E2=80=93i=C2=BB)
pg_base= backup: consejo: Pruebe =C2=ABpg_basebackup --help=C2=BB para mayor informa= ci=C3=B3n.


=
I've tried your command line, and I have the same error. The minus= sign is not the good one. Try:

pg_basebackup -c f= ast -P -D /var/lib/pgsql/17/backups/devadv01/fisicos/viernes --incremental = =C2=A0/var/lib/pgsql/17/backups/devadv01/fisicos/base_plano/backup_manifest=

=C2=A0
regards

MF


El lun, 6 ene 2025 a las 16:42, Guillaume Le= large (<guil= laume@lelarge.info>) escribi=C3=B3:
Hi,
<= br>
Le=C2= =A0lun. 6 janv. 2025 =C3=A0=C2=A020:23, Mauricio Fernandez <mmauricio.fernandez@= gmail.com> a =C3=A9crit=C2=A0:
Hi admins, I'm trying to execute= an incremental backup and I'm getting the following error

[postgres@buda ~]$ pg_basebackup -c fast -P -D $PGBKP/fisicos/vie= rnes =E2=80=93-incremental=3D$PGBKP/fisicos/base_plano/backup_manifest<= /div>
pg_basebackup: error: demasiados argumentos en la l=C3=ADnea de = =C3=B3rdenes (el primero es =C2=AB=E2=80=93-incremental=3D/var/lib/pgsql/17= /backups/devadv01/fisicos/base_tar/backup_manifest=C2=BB)
pg_basebackup:= consejo: Pruebe =C2=ABpg_basebackup --help=C2=BB para mayor informaci=C3= =B3n.

The literal translation of the er= ror message is: pg_basebackup: error: too many arguments in the command lin= e (the first is =C2=AB=E2=80=93-incremental=3D/var/lib/pgsql/17/backups/dev= adv01/fisicos/base_tar/backup_manifest=C2=BB)

<= /div>

It looks like it thinks that=C2= =A0 "--incremental=3D/var/lib/pgsql/17/backups/devadv01/fisicos/base_t= ar/backup_manifest" is one argument rather than an argument and its va= lue. Try getting rid of the equal value. Maybe it will help.


--
Guillaume.
=


--
Guillaume.
<= /div>
--0000000000000d9287062b0f2eec--