[BUGS] BUG #8272: Unable to connect to diffrent schema from jdbc

2013-06-30 Thread emesika
The following bug has been logged on the website:

Bug reference:  8272
Logged by:  Eli Mesika
Email address:  emes...@redhat.com
PostgreSQL version: 8.4.17
Operating system:   Linux (Fedora 18)
Description:

Hi
Postgres does not support currently defining the schema in teh connection
parameters which makes it imposible to seprate the database to several
schemas and connect to the right one from the application.


There is already a thread discussing that and a suggested patch that is
fixing that.
See


http://www.postgresql.org/message-id/4873f034.8010...@scharp.org




-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


[BUGS] BUG #7817: psql does not relate to footer settings in extended mode

2013-01-21 Thread emesika
The following bug has been logged on the website:

Bug reference:  7817
Logged by:  Eli Mesika
Email address:  emes...@redhat.com
PostgreSQL version: 9.1.7
Operating system:   Fedora 16
Description:

psql does not relate to footer settings in extended mode
Sometimes we need to run a sql command withot generating header and footer.
This can be done using the -t flag and --pset=footer=off
The problem is that the footer is still diaplyed even if it was set to off
if we use the extended mode for the query (-x flag)

Steps to Reproduce:
1) create a table without any data
for example
create table text(i int);
2) run
psql -U  -t --pset=footer=off 
3) No output is generated
4) run
psql -U  -t --pset=footer=off -x 
5) Output generated : "(No Rows)"

Actual results:
psql does not honour the footer settings when output is defined to be in
Extended Mode

Expected results:
psql should not generate any output is query has no results and -t and 
--pset=footer=off were given




-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


[BUGS] BUG #7792: pg_dump does not treat -c flag correctly when using tar format

2013-01-06 Thread emesika
The following bug has been logged on the website:

Bug reference:  7792
Logged by:  Eli Mesika
Email address:  emes...@redhat.com
PostgreSQL version: 9.1.7
Operating system:   Fedora 16
Description:

steps to reproduce (aasuming database name is : test)

1) pg_dump -F t -U postgres -f test.tar test
2) tar xvf test.tar  to any directory
3) vi restore.sql
* restore.sql includes DROP statements for each object even tough -c flag
was not given

repeat the above using plain-text format
1) pg_dump -F p -U postgres -f test.sql test
2) vi test.sql

This time test.sql does not include DROP staements for each object

* pg_dump should not produce DROP statements for each object if -c flag was
not given to the command






-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs