Hi,
Here is where postgres is located on the server:
ps auxw | grep postgres | grep -- -D
postgres 1740 0.0 0.0 160284 7616 ?S02: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)
t...@brownpapertickets.com 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: tma...@ecognizant.com mailto:tma...@ecognizant.com
Date: Sun, 9 Aug 2015 14:03:28 -0500
To: aolserver-talk@lists.sourceforge.net
mailto:aolserver-talk@lists.sourceforge.net
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
aolserver-talk@lists.sourceforge.net
mailto:aolserver-talk@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/aolserver-talk
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
--
___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
mailto:aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
--
___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
mailto:aolserver-talk@lists.sourceforge.net
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
--
___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk