-
Notifications
You must be signed in to change notification settings - Fork 67
ERROR: could not find junk tableoid1 column #129
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
Comments
HI @DmitriyAr, I'm sorry, but I couldn't reproduce your issue on PostgreSQL 9.5, 9.6 and 10. What exactly is broken? |
Also, could you show us your PostgreSQL and pg_pathman's versions? |
Sorry I ommited the last statement which caused the error PostgreSQL 9.5.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17), 64-bit |
Thanks, now the problem is obvious to me. Let's see what we can do. |
Unfortunately I found that my issue #77 is not have been solved.
If pg_pathman is enabled for this table the exception does not occur |
Why do you mix several problems in a single issue? You could reply to #77. |
No problem. |
Unfortunately, it's not quite true. |
Pushed a bunch of fixes to master branch. Could you test it? |
It works. Thanks. |
Steps to reproduce:
If disable pg_pathman for the table:
SELECT public.disable_pathman_for('public._journal'::regclass);
SELECT .. FOR UPDATE is OK.
The text was updated successfully, but these errors were encountered: