Обсуждение: [NOVCE] Describe Table Problems
Hi list,
I'm currently having problems trying to describe a table in one of my database servers. Here's the error:
backoffice_t2=# \d control.storedate_done
ERROR: column t.tgconstraint does not exist
LINE 3: WHERE t.tgrelid = '1154864' AND t.tgconstraint = 0
^
backoffice_t2=#
Even in phpPgAdmin, I could not check the description of the table. Is there another way for me to check the table? I just want to see what triggers are created in a specific table.
TIA,
Ridvan
--
リヅバン バルヨス
ridvan.baluyos@qualservcentral.com
http://ridvan.baluyos.net
http://www.onxiam.com/people/rbaluyos
Registered Linux User #439466
Registered Ubuntu User #16034
Q: Have you heard of the Object-Oriented way to get wealthy?
A: Inheritance.
I'm currently having problems trying to describe a table in one of my database servers. Here's the error:
backoffice_t2=# \d control.storedate_done
ERROR: column t.tgconstraint does not exist
LINE 3: WHERE t.tgrelid = '1154864' AND t.tgconstraint = 0
^
backoffice_t2=#
Even in phpPgAdmin, I could not check the description of the table. Is there another way for me to check the table? I just want to see what triggers are created in a specific table.
TIA,
Ridvan
--
リヅバン バルヨス
ridvan.baluyos@qualservcentral.com
http://ridvan.baluyos.net
http://www.onxiam.com/people/rbaluyos
Registered Linux User #439466
Registered Ubuntu User #16034
Q: Have you heard of the Object-Oriented way to get wealthy?
A: Inheritance.
"Ridvan Lakas ng Bayan S. Baluyos" <ridvan@baluyos.net> writes: > I'm currently having problems trying to describe a table in one of my > database servers. Here's the error: > backoffice_t2=# \d control.storedate_done > ERROR: column t.tgconstraint does not exist > LINE 3: WHERE t.tgrelid = '1154864' AND t.tgconstraint = 0 > ^ You're apparently trying to use an 8.3 psql with an 8.2 or older server. It should have warned you when you started it, like so: WARNING: You are connected to a server with major version 8.2, but your psql client is major version 8.3. Some backslash commands, such as \d, might not work properly. > Even in phpPgAdmin, I could not check the description of the table. ... and I'll bet your phpPgAdmin is out of sync too. As of 8.4, psql's \d commands work with a range of older server versions, but in every preceding release they are quite version-specific. I don't know the exact story on cross-version compatibility for phpPgAdmin, but it sounds like it's version-specific as well. regards, tom lane
Hi Tom,
I didn't receive any warnings upon entering the postgres server.
My client version is psql (PostgreSQL) 8.3.5.
My database server version is EnterpriseDB 8.3.0.12 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.1.0
Would it make a difference?
Ridvan
--
リヅバン バルヨス
ridvan.baluyos@qualservcentral.com
http://ridvan.baluyos.net
http://www.onxiam.com/people/rbaluyos
Registered Linux User #439466
Registered Ubuntu User #16034
Q: Have you heard of the Object-Oriented way to get wealthy?
A: Inheritance.
I didn't receive any warnings upon entering the postgres server.
My client version is psql (PostgreSQL) 8.3.5.
My database server version is EnterpriseDB 8.3.0.12 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.1.0
Would it make a difference?
Ridvan
On Tue, Aug 4, 2009 at 11:38 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Ridvan Lakas ng Bayan S. Baluyos" <ridvan@baluyos.net> writes:You're apparently trying to use an 8.3 psql with an 8.2 or older server.
> I'm currently having problems trying to describe a table in one of my
> database servers. Here's the error:
> backoffice_t2=# \d control.storedate_done
> ERROR: column t.tgconstraint does not exist
> LINE 3: WHERE t.tgrelid = '1154864' AND t.tgconstraint = 0
> ^
It should have warned you when you started it, like so:
WARNING: You are connected to a server with major version 8.2,
but your psql client is major version 8.3. Some backslash commands,
such as \d, might not work properly.... and I'll bet your phpPgAdmin is out of sync too.
> Even in phpPgAdmin, I could not check the description of the table.
As of 8.4, psql's \d commands work with a range of older server
versions, but in every preceding release they are quite
version-specific. I don't know the exact story on cross-version
compatibility for phpPgAdmin, but it sounds like it's version-specific
as well.
regards, tom lane
--
リヅバン バルヨス
ridvan.baluyos@qualservcentral.com
http://ridvan.baluyos.net
http://www.onxiam.com/people/rbaluyos
Registered Linux User #439466
Registered Ubuntu User #16034
Q: Have you heard of the Object-Oriented way to get wealthy?
A: Inheritance.
Hi 2009/8/4 Ridvan Lakas ng Bayan S. Baluyos <ridvan@baluyos.net>: > Hi Tom, > > I didn't receive any warnings upon entering the postgres server. > > My client version is psql (PostgreSQL) 8.3.5. > My database server version is EnterpriseDB 8.3.0.12 on > x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.1.0 > > Would it make a difference? Yes, even if you did not get a warning, what Tom said is valid. If I understood him correctly, though, you could use a psql from PostgreSQL 8.4 and it should work. Is that right, Tom? > Ridvan > > On Tue, Aug 4, 2009 at 11:38 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> >> "Ridvan Lakas ng Bayan S. Baluyos" <ridvan@baluyos.net> writes: >> > I'm currently having problems trying to describe a table in one of my >> > database servers. Here's the error: >> >> > backoffice_t2=# \d control.storedate_done >> > ERROR: column t.tgconstraint does not exist >> > LINE 3: WHERE t.tgrelid = '1154864' AND t.tgconstraint = 0 >> > ^ >> >> You're apparently trying to use an 8.3 psql with an 8.2 or older server. >> It should have warned you when you started it, like so: >> >> WARNING: You are connected to a server with major version 8.2, >> but your psql client is major version 8.3. Some backslash commands, >> such as \d, might not work properly. >> >> > Even in phpPgAdmin, I could not check the description of the table. >> >> ... and I'll bet your phpPgAdmin is out of sync too. >> >> As of 8.4, psql's \d commands work with a range of older server >> versions, but in every preceding release they are quite >> version-specific. I don't know the exact story on cross-version >> compatibility for phpPgAdmin, but it sounds like it's version-specific >> as well. >> >> regards, tom lane -- Michael Wood <esiotrot@gmail.com>
"Ridvan Lakas ng Bayan S. Baluyos" <ridvan@baluyos.net> writes: > My client version is psql (PostgreSQL) 8.3.5. > My database server version is EnterpriseDB 8.3.0.12 on > x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.1.0 EDB huh? Maybe you had better ask them for support. I don't know whether EDB's idea of 8.3.0 is the same as ours ... but if it's missing pg_trigger.tgconstraint, that would suggest not ... regards, tom lane
2009/8/4 Michael Wood <esiotrot@gmail.com>: > Hi > > 2009/8/4 Ridvan Lakas ng Bayan S. Baluyos <ridvan@baluyos.net>: >> Hi Tom, >> >> I didn't receive any warnings upon entering the postgres server. >> >> My client version is psql (PostgreSQL) 8.3.5. >> My database server version is EnterpriseDB 8.3.0.12 on >> x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.1.0 >> >> Would it make a difference? > > Yes, even if you did not get a warning, what Tom said is valid. If I > understood him correctly, though, you could use a psql from PostgreSQL > 8.4 and it should work. Is that right, Tom? Sorry, I misread 8.3.0 as 8.0. -- Michael Wood <esiotrot@gmail.com>