On 5/2/24 02:20, Fire Emerald wrote:
I didn't used pg_dump/restore until today and finally found my mistake
which lead to the "problem" described below.
The output "depends on" comes from the -l (l as Lima) flag, what i
wanted was the -1 (number one) flag, which stands for single transaction
I didn't used pg_dump/restore until today and finally found my mistake
which lead to the "problem" described below.
The output "depends on" comes from the -l (l as Lima) flag, what i wanted
was the -1 (number one) flag, which stands for single transaction in
pg_restore. As -l does not execute
On 3/28/24 08:57, Fire Emerald wrote:
Am 28. März 2024 15:00:06 schrieb Tom Lane :
Fire Emerald writes:
Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
output this:
5145 0 730750 TABLE subpartitions backends_y2024w03 userA
; depends on: 237
and so on
Fire Emerald writes:
> The partitioning must be the problem somehow.
[ shrug... ] You're still not providing any details that would
let somebody else reproduce or diagnose the problem.
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
regards, tom lane
Am 28. März 2024 15:00:06 schrieb Tom Lane :
Fire Emerald writes:
Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
output this:
5145 0 730750 TABLE subpartitions backends_y2024w03 userA
;depends on: 237
and so on ...
That is not an error, it's just
Fire Emerald writes:
> Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
> output this:
> 5145 0 730750 TABLE subpartitions backends_y2024w03 userA
> ;depends on: 237
> and so on ...
That is not an error, it's just verbose display of one of the items
in the
Hello everyone,
I created a database dump in postgres 'custom' format using: pg_dump -d
origin --data-only -Fc > file.dump
Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
output this:
5145 0 730750 TABLE subpartitions backends_y2024w03 userA
;depends on:
