Re: Help with large delete

> On Apr 16, 2022, at 13:56, Rob Sargent wrote: > > > >> On Apr 16, 2022, at 12:24 PM, Perry Smith wrote: >> >>  >> >>> On Apr 16, 2022, at 12:57, Jan Wieck >> > wrote: >>> >>> Make your connection immune to disconnects by using something like the >>> screen

Re: Help with large delete

On Apr 16, 2022, at 12:24 PM, Perry Smith wrote:On Apr 16, 2022, at 12:57, Jan Wieck wrote:Make your connection immune to disconnects by using something like the screen utility.Exactly… I’m using emacs in a server (daemon) mode so it stays alive.  Then I do “shell” within it.I

Re: Help with large delete

> On Apr 16, 2022, at 12:57, Jan Wieck wrote: > > Make your connection immune to disconnects by using something like the screen > utility. Exactly… I’m using emacs in a server (daemon) mode so it stays alive. Then I do “shell” within it. > On Sat, Apr 16, 2022, 09:26 Perry Smith

Re: Help with large delete

Make your connection immune to disconnects by using something like the screen utility. Regards, Jan On Sat, Apr 16, 2022, 09:26 Perry Smith wrote: > Currently I have one table that mimics a file system. Each entry has a > parent_id and a base name where parent_id is an id in the table that

Re: ***SPAM*** Re: Help with large delete

Perry Smith writes: > On Apr 16, 2022, at 10:33, Tom Lane wrote: >> The most obvious question is do you have an index on the referencing >> column. PG doesn't require one to exist to create an FK; but if you >> don't, deletes of referenced rows had better be uninteresting to you >>

Re: ***SPAM*** Re: Help with large delete

> On Apr 16, 2022, at 10:33, Tom Lane wrote: > > Perry Smith writes: >> Currently I have one table that mimics a file system. Each entry has a >> parent_id and a base name where parent_id is an id in the table that must >> exist in the table or be null with cascade on delete. >> I’ve

Re: Require details that can we see the password history to a User account in PostgreSQL Database.

On 4/16/22 00:31, Sonai muthu raja M wrote: Dear Adrian, Yes, exactly. My query regardingan application user that when passwords were changed and what the previous values were? 1) Postgres has not built in process to audit changes to it's own roles. 2) That also means it does not audit

Re: Help with large delete

Perry Smith writes: > Currently I have one table that mimics a file system. Each entry has a > parent_id and a base name where parent_id is an id in the table that must > exist in the table or be null with cascade on delete. > I’ve started a delete of a root entry with about 300,000

Re: Help with large delete

On 2022-04-16 08:25:56 -0500, Perry Smith wrote: > Currently I have one table that mimics a file system. Each entry has > a parent_id and a base name where parent_id is an id in the table that > must exist in the table or be null with cascade on delete. > > I’ve started a delete of a root entry

Re: Help with large delete

On 4/16/22 07:25, Perry Smith wrote: Currently I have one table that mimics a file system. Each entry has a parent_id and a base name where parent_id is an id in the table that must exist in the table or be null with cascade on delete. I’ve started a delete of a root entry with about 300,000

Help with large delete

Currently I have one table that mimics a file system. Each entry has a parent_id and a base name where parent_id is an id in the table that must exist in the table or be null with cascade on delete. I’ve started a delete of a root entry with about 300,000 descendants. The table currently has