[AOLSERVER] Aolserver - Postgresql - not recognizing columns added to tables

3 views
Skip to first unread message

Thorpe Mayes

unread,
Aug 9, 2015, 3:16:19 PM8/9/15
to aolserv...@lists.sourceforge.net
Hi,

I have moved postgresql databases from one server to another. This was done by dumping the database, moving the resulting file to the new server, and then restoring the dumped file on the new server.

When I directly select rows via postgresdql (on the new server) from a table that had a column added after the table was created and before the table was moved to the new server there are not any problems.

However, when I try to do the same select from within a tcl script an error is thrown - the column does not exist. When I run the sql statement without the offending column, there is not a problem. 

So, it appears to me that the problem is with columns that have been added to tables via alter table…

Can anyone shed some light on this problem?

Thank you,

Thorpe

Thorpe Mayes
eCognizant LLC
2313 Lockhill-Selma Road, Ste 164
San Antonio, TX 78230






Ayan George

unread,
Aug 9, 2015, 3:54:17 PM8/9/15
to aolserv...@lists.sourceforge.net


On 08/09/2015 03:03 PM, Thorpe Mayes wrote:
> Hi,
>
> I have moved postgresql databases from one server to another. This
> was done by dumping the database, moving the resulting file to the
> new server, and then restoring the dumped file on the new server.
>
> When I directly select rows via postgresdql (on the new server) from
> a table that had a column added after the table was created and
> before the table was moved to the new server there are not any
> problems.
>
> However, when I try to do the same select from within a tcl script
> an error is thrown - the column does not exist. When I run the sql
> statement without the offending column, there is not a problem.
>
> So, it appears to me that the problem is with columns that have been
> added to tables via alter table…
>
> Can anyone shed some light on this problem?
>

What version of PostgreSQL are you running and which version of libpq is
your nspostgres linked against?

When you moved servers, did you also change the version of postgres
you're using?

-ayan

------------------------------------------------------------------------------
_______________________________________________
aolserver-talk mailing list
aolserv...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk

Ayan George

unread,
Aug 9, 2015, 4:22:26 PM8/9/15
to aolserv...@lists.sourceforge.net

Also, can you see the new columns by searching the information schema in
both psql and aolserver?

Peter Sadlon

unread,
Aug 9, 2015, 8:44:48 PM8/9/15
to Thorpe Mayes, aolserv...@lists.sourceforge.net
Just to better understand your problem, this was the order of events?

old server: create table
old server: alter table add column
old server: select any/all columns work

copy to new server

new server: select from original columns work with postgresdql 
new server: select from an added column works with postgresdql 
new server: select from original columns work with tcl 
new server: select from an added column FAILS with tcl 

My first guess would be to make sure your config script is connecting to the correct database/server now that you have multiple db servers.  Same thing for postgresdql.  

Are you connecting with the same username via postgresdql and tcl?

Next check your pg_dump file, do a grep for the new column name, make sure that it is included in the dump.



From: tma...@ecognizant.com
Date: Sun, 9 Aug 2015 14:03:28 -0500
To: aolserv...@lists.sourceforge.net
Subject: [AOLSERVER] Aolserver - Postgresql - not recognizing columns added to tables

Sep

unread,
Aug 9, 2015, 8:47:14 PM8/9/15
to Peter Sadlon, Thorpe Mayes, aolserv...@lists.sourceforge.net
I don't quite remember my postgresql, but I'm presuming that maybe postgresql has something like a data dictionary like in Oracle that needs syncing perhaps?

Regards.
--
"A scrum a day keeps the pigs at bay"

Tony Bennett (Brown Paper Tickets)

unread,
Aug 10, 2015, 8:19:16 AM8/10/15
to aolserv...@lists.sourceforge.net
The same select should work in tcl for the added column.  Try updating a record in postgresql and selecting the same record from tcl. If there's a mismatch then they're not connecting to the same place.

-Tony

Tony Bennett (Brown Paper Tickets)

unread,
Aug 10, 2015, 8:29:15 AM8/10/15
to aolserv...@lists.sourceforge.net
Also I'm curious to know if there's anything special about the new columns.  Are they encrypted or a strange datatype?  If it's a newish type of field then the tcl might need updating to use it.

Thorpe Mayes

unread,
Aug 10, 2015, 10:37:13 AM8/10/15
to Tony Bennett (Brown Paper Tickets), aolserv...@lists.sourceforge.net
Hi,

Here is where postgres is located on the server:

ps auxw |  grep postgres | grep -- -D
postgres  1740  0.0  0.0 160284  7616 ?        S    02:49   0:00 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data


Here is how I installed nspostgres-4.1:

make install AOLSERVER=/usr/local/aolserver  POSTGRES=/usr/local/pgsql

Thorpe


_______________________________________________ aolserver-talk mailing list aolserv...@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/aolserver-talk


------------------------------------------------------------------------------


_______________________________________________
aolserver-talk mailing list
aolserv...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk

------------------------------------------------------------------------------
_______________________________________________
aolserver-talk mailing list
aolserv...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
Reply all
Reply to author
Forward
0 new messages