BUG #3985: select command not working
The following bug has been logged online:
Bug reference: 3985
Logged by: srijit
Email address: srijit219@yahoo.com
PostgreSQL version: 8.1
Operating system: windows xp sp2
Description: select command not working
Details:
i`ve installed Postgresql 8.1.....i`m able to create databases and tables
but wen i try to view the contents of a table i get a message called "more
is not a recognised internal command"., this has happened in many of my
friends PCs also..... i request u to kindly give us a solution to this
prob.....
i`ve used the following statements
create user srijit with password 'admin';
CREATE ROLE
create database mydb owner srijit;
DATABASE CREATED
\c mydb srijit;
password for srijit:admin
create table tab1(sno integer);
table created
insert into tab1 values(10);
INSERT 0 1
select * from tab1;
'more' is not a recognised internal or external command
On Sun, Feb 24, 2008 at 12:05:36PM +0000, srijit wrote:
The following bug has been logged online:
Bug reference: 3985
Logged by: srijit
Email address: srijit219@yahoo.com
PostgreSQL version: 8.1
Operating system: windows xp sp2
Description: select command not working
Details:i`ve installed Postgresql 8.1.....i`m able to create databases and tables
but wen i try to view the contents of a table i get a message called "more
is not a recognised internal command"., this has happened in many of my
friends PCs also..... i request u to kindly give us a solution to this
prob.....i`ve used the following statements
create user srijit with password 'admin';
CREATE ROLEcreate database mydb owner srijit;
DATABASE CREATED\c mydb srijit;
password for srijit:admincreate table tab1(sno integer);
table createdinsert into tab1 values(10);
INSERT 0 1select * from tab1;
'more' is not a recognised internal or external command
That's interesting, indeed. AFAIK all windows versions ever has had a
more.com available - it shuold bei n your SYSTEM32 directory. Please check
if it's there, and if it could be the permissions on the file that are
somehow broken?
If you don't have it or it's somehow broken in a differnt way, you can run
the command:
\pset pager
in psql, to turn off the usage of the pager. You'll then of course not get
a pager, but you should get your data.
//Magnus