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.

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

late binding view introspection conflicts with drop statements on Redshift #1305

Closed
drewbanin opened this issue Feb 20, 2019 · 1 comment
Closed
Labels
help_wanted Trickier changes, with a clear starting point, good for previous/experienced contributors redshift

Comments

@drewbanin
Copy link
Contributor

Issue

Issue description

A drop statement run concurrently with a query to pg_get_late_binding_view_cols() will cause the pg_get_late_binding_view_cols() query to fail with something like:

ERROR:  table 6616765 dropped by concurrent transaction

I posted this (apparent) Redshift bug to the AWS Redshift forum, but also wanted to track it here. Check out the post for more info: https://forums.aws.amazon.com/thread.jspa?threadID=298770

This can be reproduced using the scripts here: https://gist.github.com/drewbanin/98beec96edadfe25398a79a8274b2cdb

I think we're blocked on Redshift fixing this, but very open to any clever ideas here. One way to mitigate this would be to cache introspective queries during parsing, which I will create a separate issue for.

@drewbanin drewbanin added help_wanted Trickier changes, with a clear starting point, good for previous/experienced contributors redshift labels Feb 20, 2019
@drewbanin
Copy link
Contributor Author

The Redshift forum link above indicates that this bug is fixed! Closing (and crossing my fingers 🤞)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help_wanted Trickier changes, with a clear starting point, good for previous/experienced contributors redshift
Projects
None yet
Development

No branches or pull requests

1 participant