For work planning, create a temporary table, copy from a generated data
set, and test it out. It really depends. Normally, you don't iterate in SQL
since rows are assumed to be independent. You think about SQL in terms of
sets and let application code handle the data transfers. It also really
depen
Thanks, Karsten,
I would like the information to work planning purpose.
Regards,
David
On Sat, 2 Apr 2022 at 14:47, Karsten Hilbert
wrote:
> > > On Apr 1, 2022, at 10:18 PM, Ron wrote:
> > >
> > > On 4/1/22 20:34, Shaozhong SHI wrote:
> > >>
> > >> I have a script running to iterate over 4
> > On Apr 1, 2022, at 10:18 PM, Ron wrote:
> >
> > On 4/1/22 20:34, Shaozhong SHI wrote:
> >>
> >> I have a script running to iterate over 4-5 million rows. It keeps
> >> showing up in red in PgAdmin. It remains active.
> >>
> >> How long does iteration over 4-5 million rows usually take?
> On Apr 1, 2022, at 10:18 PM, Ron wrote:
>
> On 4/1/22 20:34, Shaozhong SHI wrote:
>>
>> I have a script running to iterate over 4-5 million rows. It keeps showing
>> up in red in PgAdmin. It remains active.
>>
>> How long does iteration over 4-5 million rows usually take?
4-5 million
On 4/1/22 20:34, Shaozhong SHI wrote:
I have a script running to iterate over 4-5 million rows. It keeps
showing up in red in PgAdmin. It remains active.
How long does iteration over 4-5 million rows usually take?
What /*exactly*/ are you doing?
--
Angular momentum makes the world go 'r
On 4/1/22 18:34, Shaozhong SHI wrote:
I have a script running to iterate over 4-5 million rows. It keeps
showing up in red in PgAdmin. It remains active.
How long does iteration over 4-5 million rows usually take?
Given that there is no real information provided in the problem
descriptio
