Okay - that worked.
How did you know that would work? That's incredible.
On Sun, May 7, 2023 at 4:25 PM Tom Lane wrote:
> "Michael P. McDonnell" writes:
> > I have 2 stored procedures that need to run back to back. It could
> > convert to a single one - but it's easier from a maintenance perspe
"Michael P. McDonnell" writes:
> On Sun, May 7, 2023 at 4:25 PM Tom Lane wrote:
>> Perhaps an "ANALYZE table_b" in between would help.
> Okay - that worked.
> How did you know that would work? That's incredible.
Well, I guessed ;-) ... but it was a well-educated guess.
The symptoms sounded lik
"Michael P. McDonnell" writes:
> I have 2 stored procedures that need to run back to back. It could
> convert to a single one - but it's easier from a maintenance perspective to
> keep them separated.
> The first procedure effectively is
> INSERT INTO table_b () SELECT FROM _table_a_;
> COMM
Hey team -
I have 2 stored procedures that need to run back to back. It could
convert to a single one - but it's easier from a maintenance perspective to
keep them separated.
The first procedure effectively is
INSERT INTO table_b () SELECT FROM _table_a_;
COMMIT;
Total execution time - about
