Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: data replicated from PG becomes invisible after restarting MyDuck Server #230

Merged
merged 12 commits into from
Nov 28, 2024
Merged

fix: data replicated from PG becomes invisible after restarting MyDuck Server #230

merged 12 commits into from
Nov 28, 2024

Conversation

TianyuZhang1214
Copy link
Contributor

No description provided.

@TianyuZhang1214 TianyuZhang1214 linked an issue Nov 28, 2024 that may be closed by this pull request
Data Replicated from PG Becomes Invisible After Restarting MyDuck Server #216
Closed
@fanyang01
Copy link
Collaborator

COPY DATABASE is too tricky to make it work properly. Let's use CREATE TABLE t AS FROM pg.t for now.

@fanyang01 fanyang01 marked this pull request as ready for review November 28, 2024 14:22
@fanyang01 fanyang01 merged commit e536c63 into main Nov 28, 2024
8 checks passed
@TianyuZhang1214 TianyuZhang1214 deleted the 216-data-replicated-from-pg-becomes-invisible branch December 26, 2024 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Data Replicated from PG Becomes Invisible After Restarting MyDuck Server
2 participants
@TianyuZhang1214 @fanyang01