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

Unable to see the fdw table in pgadmin? #29

Closed
johnmudd opened this Issue Oct 11, 2013 · 4 comments

Comments

Projects
None yet
3 participants
@johnmudd

I created a csv fdw table following the example. I'm able to access the table and it works well. So I had another person connect to my db from a separate PC using pgadmin. They can't see the fdw table. Even thought they are using my user account.

If I create a regular table then that appears in pgAdmin. But not the fdw table from a remote PC.

Any suggestions?

I assume this has nothing to do with multicorn. I'm just posting this here so I can share my experience in case it helps others.

@davidcrawford

This comment has been minimized.

Show comment
Hide comment
@davidcrawford

davidcrawford Oct 11, 2013

Contributor

Foreign tables don't show up in pg_table, but have their own catalog table
instead (I think it's pg_foreign_table). That might explain why pgAdmin
doesn't show them. I don't believe the user needs usage privileges on the
fdw in order to see tables, but it's possible, maybe try that?

On Fri, Oct 11, 2013 at 11:51 AM, johnmudd notifications@github.com wrote:

I created a csv fdw table following the example. I'm able to access the
table and it works well. So I had another person connect to my db from a
separate PC using pgadmin. They can't see the fdw table. Even thought they
are using my user account.

If I create a regular table then that appears in pgAdmin. But not the fdw
table from a remote PC.

Any suggestions?

I assume this has nothing to do with multicorm. I'm just posting this here
so I can share my experience in case it helps others.


Reply to this email directly or view it on GitHubhttps://github.com/Kozea/Multicorn/issues/29
.

Contributor

davidcrawford commented Oct 11, 2013

Foreign tables don't show up in pg_table, but have their own catalog table
instead (I think it's pg_foreign_table). That might explain why pgAdmin
doesn't show them. I don't believe the user needs usage privileges on the
fdw in order to see tables, but it's possible, maybe try that?

On Fri, Oct 11, 2013 at 11:51 AM, johnmudd notifications@github.com wrote:

I created a csv fdw table following the example. I'm able to access the
table and it works well. So I had another person connect to my db from a
separate PC using pgadmin. They can't see the fdw table. Even thought they
are using my user account.

If I create a regular table then that appears in pgAdmin. But not the fdw
table from a remote PC.

Any suggestions?

I assume this has nothing to do with multicorm. I'm just posting this here
so I can share my experience in case it helps others.


Reply to this email directly or view it on GitHubhttps://github.com/Kozea/Multicorn/issues/29
.

@johnmudd

This comment has been minimized.

Show comment
Hide comment
@johnmudd

johnmudd Oct 11, 2013

Thanks David!

Your clue led me to this bug report and solution. It was just a pgAdmin setting that needed to be turned on. I don't use pgAdmin myself (not yet, at least) so I was in the dark.

Thanks David!

Your clue led me to this bug report and solution. It was just a pgAdmin setting that needed to be turned on. I don't use pgAdmin myself (not yet, at least) so I was in the dark.

@johnmudd

This comment has been minimized.

Show comment
Hide comment
@johnmudd

johnmudd Oct 11, 2013

We changed the pgAdmin setting and it displays the fdw table now.

We changed the pgAdmin setting and it displays the fdw table now.

@johnmudd johnmudd closed this Oct 11, 2013

@84zhu

This comment has been minimized.

Show comment
Hide comment
@84zhu

84zhu Aug 11, 2016

Google answers better than Baidu‘s,3Q’ @johnmudd

84zhu commented Aug 11, 2016

Google answers better than Baidu‘s,3Q’ @johnmudd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment