Menu
▾
▴
aolserver-talk
|
From: Thorpe M. <tm...@ec...> - 2015-08-09 19:16:10
|
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 Phone: (405) 445-7877 Cell: (405) 514-9753 |
|
From: Ayan G. <ay...@ay...> - 2015-08-09 19:54:14
|
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 |
|
From: Ayan G. <ay...@ay...> - 2015-08-09 20:22:17
|
Also, can you see the new columns by searching the information schema in both psql and aolserver? |
|
From: Peter S. <f_p...@ho...> - 2015-08-10 00:44:39
|
Just to better understand your problem, this was the order of events? old server: create tableold server: alter table add columnold 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: tm...@ec... Date: Sun, 9 Aug 2015 14:03:28 -0500 To: aol...@li... Subject: [AOLSERVER] Aolserver - Postgresql - not recognizing columns added to tables 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 MayeseCognizant LLC2313 Lockhill-Selma Road, Ste 164San Antonio, TX 78230Phone: (405) 445-7877Cell: (405) 514-9753 ------------------------------------------------------------------------------ _______________________________________________ aolserver-talk mailing list aol...@li... https://lists.sourceforge.net/lists/listinfo/aolserver-talk |
|
From: Sep <the...@gm...> - 2015-08-10 00:47:05
|
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. 2015-08-10 8:44 GMT+08:00 Peter Sadlon <f_p...@ho...>: > 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: tm...@ec... > Date: Sun, 9 Aug 2015 14:03:28 -0500 > To: aol...@li... > Subject: [AOLSERVER] Aolserver - Postgresql - not recognizing columns > added to tables > > > 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 > Phone: (405) 445-7877 > Cell: (405) 514-9753 > > > > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ aolserver-talk mailing > list aol...@li... > https://lists.sourceforge.net/lists/listinfo/aolserver-talk > > > ------------------------------------------------------------------------------ > > _______________________________________________ > aolserver-talk mailing list > aol...@li... > https://lists.sourceforge.net/lists/listinfo/aolserver-talk > > -- "A scrum a day keeps the pigs at bay" |
|
From: Tony B. (B. P. Tickets) <to...@br...> - 2015-08-10 12:19:09
|
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 On 8/9/15 5:44 PM, Peter Sadlon wrote: > 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: tm...@ec... > Date: Sun, 9 Aug 2015 14:03:28 -0500 > To: aol...@li... > Subject: [AOLSERVER] Aolserver - Postgresql - not recognizing columns > added to tables > > 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 > Phone: (405) 445-7877 > Cell: (405) 514-9753 > > > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ aolserver-talk mailing > list aol...@li... > https://lists.sourceforge.net/lists/listinfo/aolserver-talk > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > aolserver-talk mailing list > aol...@li... > https://lists.sourceforge.net/lists/listinfo/aolserver-talk |
|
From: Tony B. (B. P. Tickets) <to...@br...> - 2015-08-10 12:29:09
|
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. On 8/10/15 5:05 AM, Tony Bennett (Brown Paper Tickets) wrote: > 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 > > On 8/9/15 5:44 PM, Peter Sadlon wrote: >> 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: tm...@ec... >> Date: Sun, 9 Aug 2015 14:03:28 -0500 >> To: aol...@li... >> Subject: [AOLSERVER] Aolserver - Postgresql - not recognizing columns >> added to tables >> >> 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 >> Phone: (405) 445-7877 >> Cell: (405) 514-9753 >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ aolserver-talk >> mailing list aol...@li... >> https://lists.sourceforge.net/lists/listinfo/aolserver-talk >> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> aolserver-talk mailing list >> aol...@li... >> https://lists.sourceforge.net/lists/listinfo/aolserver-talk > |
|
From: Thorpe M. <tm...@ec...> - 2015-08-10 14:37:03
|
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 > On Aug 10, 2015, at 7:05 AM, Tony Bennett (Brown Paper Tickets) <to...@br...> wrote: > > 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 > > On 8/9/15 5:44 PM, Peter Sadlon wrote: >> 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: tm...@ec... <mailto:tm...@ec...> >> Date: Sun, 9 Aug 2015 14:03:28 -0500 >> To: aol...@li... <mailto:aol...@li...> >> Subject: [AOLSERVER] Aolserver - Postgresql - not recognizing columns added to tables >> >> 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 >> Phone: (405) 445-7877 >> Cell: (405) 514-9753 >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ aolserver-talk mailing list aol...@li... <mailto:aol...@li...>https://lists.sourceforge.net/lists/listinfo/aolserver-talk <https://lists.sourceforge.net/lists/listinfo/aolserver-talk> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> aolserver-talk mailing list >> aol...@li... <mailto:aol...@li...> >> https://lists.sourceforge.net/lists/listinfo/aolserver-talk <https://lists.sourceforge.net/lists/listinfo/aolserver-talk> > > ------------------------------------------------------------------------------ > _______________________________________________ > aolserver-talk mailing list > aol...@li... <mailto:aol...@li...> > https://lists.sourceforge.net/lists/listinfo/aolserver-talk <https://lists.sourceforge.net/lists/listinfo/aolserver-talk> Thank you, Thorpe Thorpe Mayes eCognizant LLC 2313 Lockhill-Selma Road, Ste 164 San Antonio, TX 78230 Phone: (405) 445-7877 Cell: (405) 514-9753 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X