···11{
22 "db_name": "PostgreSQL",
33- "query": "SELECT collection, rkey, record_cid FROM records WHERE repo_id = $1 AND (collection, rkey) > ($2, $3) ORDER BY collection, rkey LIMIT $4",
33+ "query": "SELECT collection, rkey, record_cid FROM records WHERE repo_id = $1",
44 "describe": {
55 "columns": [
66 {
···2121 ],
2222 "parameters": {
2323 "Left": [
2424- "Uuid",
2525- "Text",
2626- "Text",
2727- "Int8"
2424+ "Uuid"
2825 ]
2926 },
3027 "nullable": [
···3330 false
3431 ]
3532 },
3636- "hash": "ff7899984ea138f1e608fa862def47402369a428ac9116c653890e5fcaa0015b"
3333+ "hash": "72d9db2d1287fa43f69666a5259d3243e5d87807551565948ab99f1400b8cc4c"
3734}
-9
KNOWN_ISSUES.md
···11-# Known Issues
22-33-## Account migration from bsky.social
44-55-Migrating your account from bsky.social to this PDS works, but Bluesky's appview may not recognize your new signing key. This means you can post and your followers will see it, but some authenticated requests might fail with "jwt signature does not match jwt issuer".
66-77-We've been trying hard to verify that our side is correct (PLC updated, signing keys match, relays have the account) but something about how we're emitting events isn't triggering Bluesky's appview to refresh its identity data. Still investigating.
88-99-No workaround yet.
···11+CREATE TABLE record_blobs (
22+ id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
33+ repo_id UUID NOT NULL REFERENCES users(id) ON DELETE CASCADE,
44+ record_uri TEXT NOT NULL,
55+ blob_cid TEXT NOT NULL,
66+ created_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
77+ UNIQUE(repo_id, record_uri, blob_cid)
88+);
99+1010+CREATE INDEX idx_record_blobs_repo_id ON record_blobs(repo_id);
1111+CREATE INDEX idx_record_blobs_blob_cid ON record_blobs(blob_cid);