Tom Lane írta:
Bob Lunney bob_lun...@yahoo.com writes:
I have a job that summarizes some data from a table, truncates the table,
drops the indexes, writes the summarized data back into the table, then
recreates the indexes. The operations above are not in a single
transaction, but
Boszormenyi Zoltan z...@cybertec.at writes:
I looked at ruleutils.c and now I am a little confused.
I mean different functions use different subsystems to
get their info. E.g.:
Yup.
Am I missing something?
Yes. That code is hopelessly intertwined with other operations inside
the backend
Euler Taveira de Oliveira wrote:
Tom Lane escreveu:
The window for this sort of thing isn't very large, because the first
thing pg_dump does is acquire AccessShareLock on every table it intends
to dump, and past that point it won't be possible for anyone to modify
the table's DDL. But it
I have a job that summarizes some data from a table, truncates the table, drops
the indexes, writes the summarized data back into the table, then recreates the
indexes. The operations above are not in a single transaction, but separate
statements executed by a script. Easy, runs great, has
Bob Lunney bob_lun...@yahoo.com writes:
I have a job that summarizes some data from a table, truncates the table,
drops the indexes, writes the summarized data back into the table, then
recreates the indexes. The operations above are not in a single transaction,
but separate statements
Tom Lane escreveu:
The window for this sort of thing isn't very large, because the first
thing pg_dump does is acquire AccessShareLock on every table it intends
to dump, and past that point it won't be possible for anyone to modify
the table's DDL. But it can happen.
I did not see it
