docs: troubleshoot lr, pg_subscription_rel and pgcopydb guides

[dhanushreddy291]

https://neon-next-git-fork-dhanushreddy291-add-docs-247336-neondatabase.vercel.app/docs/guides/logical-replication-pg_subscription_rel
https://neon-next-git-fork-dhanushreddy291-add-docs-247336-neondatabase.vercel.app/docs/guides/pgcopydb

[vercel]

@dhanushreddy291 is attempting to deploy a commit to the neondatabase Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
neon-next	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 12, 2025 10:45am

[bgrenon]

@dhanushreddy291 the pgcopydb doc is reviewed with some edits, mostly for concision, but with 2 new points:

• When I tested (neon to neon), --resume did not work. I think the source db needs to support traditional postgres snapshots. I've added language to that effect. Can you confirm this?
• The environment variables from Step 1 were not available to the 2nd monitoring terminal session; I added language capture you need to either set new variables, or include --source flag.

[dhanushreddy291]

@dhanushreddy291 the pgcopydb doc is reviewed with some edits, mostly for concision, but with 2 new points:

Sorry, @bgrenon. I tested LR from other providers to Neon but missed Neon-to-Neon and Neon to third-party postgres. I encountered errors today when doing that and added --no-acl for Neon-to-Neon migrations or Neon to any.

The following error is when we do pgcopydb clone --no-owner from Neon to Neon without --no-acl

The following error is when we do pgcopydb clone --no-owner from Neon to a 3rd party Postgres without --no-acl

• When I tested (neon to neon), --resume did not work. I think the source db needs to support traditional postgres snapshots. I've added language to that effect. Can you confirm this?

I also removed the resume flag and stream sentinel since they don't work without functional LR. My apologies for the oversight.

• The environment variables from Step 1 were not available to the 2nd monitoring terminal session; I added language capture you need to either set new variables, or include --source flag.

Sure. Thanks