From: | Joshua Drake <jd(at)commandprompt(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Alan Hodgson <ahodgson(at)lists(dot)simkin(dot)ca>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: vacuumdb seems not to like option -j when run from crontab |
Date: | 2023-12-05 17:56:57 |
Message-ID: | CAJvJg-QpehT51d=0=cxTOKcpT86k7JKzGsm+Ej=o6__fAsJjtg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
8.4 does not support -j
On Mon, Dec 4, 2023 at 8:22 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
> (Sorry for top-posting. Blame gmail.)
>
> Turns out that PG 8.4.20 is also installed from the RHEL repository.
>
> Thanks.
>
> On Mon, Dec 4, 2023 at 11:13 AM Alan Hodgson <ahodgson(at)lists(dot)simkin(dot)ca>
> wrote:
>
>> On Mon, 2023-12-04 at 11:07 -0500, Ron Johnson wrote:
>>
>> PG 9.6.24 (Yes, it's EOL.)
>>
>> When running "vacuumdb -p5433 -j4 --analyze tap_d" from a bash prompt, it
>> works as expected:
>> $ vacuumdb -p5433 -j4 --analyze tap_d
>> vacuumdb: vacuuming database "tap_d"
>>
>> But not when running from crontab:
>> vacuumdb -p5433 -j4 --analyze tap_d
>> vacuumdb: invalid option -- 'j'
>> Try "vacuumdb --help" for more information.
>>
>> Obviously I'm missing something, but don't see what it is. Attached is
>> the script it runs from.
>>
>>
>> Is your user and PATH the same? ie. are you running the same vacuumdb
>> executable?
>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2023-12-05 18:51:22 | Re: Emitting JSON to file using COPY TO |
Previous Message | Davin Shearer | 2023-12-05 17:43:31 | Re: Emitting JSON to file using COPY TO |