| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Shaozhong SHI <shishaozhong(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Can anyone confirm the flaw of postgres and how to deal with it? |
| Date: | 2022-04-20 15:51:42 |
| Message-ID: | CAKFQuwbbY2tQYFuq57bDOXfeWbtax6y5nkipPDe7w8P9CedtvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 20, 2022 at 8:48 AM Shaozhong SHI <shishaozhong(at)gmail(dot)com>
wrote:
> I loaded several tables onto Postgres.
>
> When you view, you can see all columns.
>
> However, there are 'ghost columns' that I remember I used before, but not
> now.
>
> select column_name::text from information_schema.columns where
> table_name=a_table
>
> keeps listing columns that I can not see in the current table.
>
> Why does this happen?
>
> What is the solution?
>
>
I'm going to assume some kind of operator error until you can prove the
observation with actual queries and output. Hopefully putting that
information together will cause you to realize where you are wrong. If not
we at least get something that is debuggable.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2022-04-20 16:05:57 | Re: Can anyone confirm the flaw of postgres and how to deal with it? |
| Previous Message | Shaozhong SHI | 2022-04-20 15:47:52 | Can anyone confirm the flaw of postgres and how to deal with it? |