Ping Yao writes:
> Thank you for the comment. I think we do. What I found odd here is the
> Query Plan (with analyze) clearly shows the actual execution to be very
> quick, that's why I don't think it's an index problem. What do you think?
I wouldn't rule it out on that basis. Foreign key enforc
On Mon, Dec 4, 2023 at 3:43 PM Ping Yao wrote:
>
> Hi Merlin,
>
> Thank you for the comment. I think we do. What I found odd here is the
> Query Plan (with analyze) clearly shows the actual execution to be very
> quick, that's why I don't think it's an index problem. What do you think?
>
I'm not
Hi Merlin,
Thank you for the comment. I think we do. What I found odd here is the
Query Plan (with analyze) clearly shows the actual execution to be very
quick, that's why I don't think it's an index problem. What do you think?
Ping
--
Pook-Ping Yao (He/Him)
Chief Technology Officer and co-Fou
On Fri, Dec 1, 2023 at 11:48 AM Ping Yao wrote:
> Hello All.
>
> First timer here, long time user though. Thank you in advance.
>
> Can someone help me understand why my simple DELETE query is so slow to
> run?
>
Not familiar with citus to diagnose any citus issues. Having said that,
can you co
(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
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 -
Add a pg binary path to script
br
Kaido
On Mon, 4 Dec 2023 at 18:13, Alan Hodgson 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 -
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 cronta
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'
> On Nov 30, 2023, at 7:53 PM, Tom Lane wrote:
>
>> Is there a way to simply disable GSSAPI authentication? I could not find it.
>
> gssencmode=disable in your connection options; but that's a tad
> inconvenient probably.
I discovered there is a PGGSSENCMODE environment variable. I set it to
