OK.understand.
I'll exclude relkind IN( 's' , 'c' ) file in backup set.
THANKS Qingqing Zhou & tom lane!
Tom Lane wrote:
> "Qingqing Zhou" <[EMAIL PROTECTED]> writes:
>
>>Pg_xactlock is always there as a special relation.
>
>
> pg_xactlock isn't really a relation. The way I think about it is
"Qingqing Zhou" <[EMAIL PROTECTED]> writes:
> Pg_xactlock is always there as a special relation.
pg_xactlock isn't really a relation. The way I think about it is that
it's a dummy entry in pg_class that exists to reserve a relation OID
for a specific purpose --- namely, we can lock transaction ID
Pg_xactlock is always there as a special relation. It has no footprint on
disk. Transactions will keep a record in pg_xactlock at the beginning and
remove the record at the end. Once any conflicting update happens, the
latter transaction will use this relation to wait for the former
transaction's r
Hi.
I'm writing backup guide and script.
I will look up on-disk-filename should be backuped
in a pg_class, like:
>SELECT oid,relfilenode,relname,relkind FROM pg_class;
it return like:
> 17173 | 17173 | sql_packages| r
> 17182 | 17182 | pg_toast_17178_index