PGsql ERROR: duplicate key value violates unique constraint "UQE_jfs_xattr_name"

[solracsf]

On the server (postgres 14.2) log, multiple entries:

ERROR:  duplicate key value violates unique constraint "UQE_jfs_xattr_name"
DETAIL:  Key (inode, name)=(1, lastBackup) already exists.
STATEMENT:  INSERT INTO "jfs_xattr" ("inode","name","value") VALUES ($1,$2,$3)

[zhijian-pro]

What is the way to reproduce, I cannot reproduce this problem by setting extended attributes when I use the postgres database as meta

[solracsf]

These are my settings:

juicefs format \
    --compress zstd \
    --trash-days 3 \
    --storage s3 \
    --shards 32 \
    --encrypt-rsa-key jfs.pem \
    --bucket https://jfs-sharder%d.s3.com \
    --access-key xxxxxxxxxx \
    --secret-key xxxxxxxx \
    postgres://jfs:[email protected]:5432/jfs \
    data

juicefs mount \
    --no-usage-report \
    --background \
    --max-uploads 256 \
    --cache-size 8192 \
    --cache-dir /var/cache/jfs-sharder \
    --log /var/log/jfs-sharder.log \
    postgres://jfs:[email protected]:5432/jfs \
    data

This has something to do with automatic metadata because if --backup-meta 0 is set on mount, error is no longer logged.

[davies]

@solracsf When we create a xattr with XattrCreateOrReplace flag, it's normal to insert it first (fail with duplicated key), then it will update it.

It's better to use upsert for PG.