Обсуждение: Where is the msi-setup described ?

> Hi folks,
>
>
> where do i get documentation about the msi-setup dialogs for
> Windows plaforms  ?

http://pginstaller.projects.postgresql.org

//Magnus

Hi folks,


where do i get documentation about the msi-setup dialogs for
Windows plaforms  ?

http://pginstaller.projects.postgresql.org

//Magnus


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

Edit postgresql.conf and set a listen_addresses that's not just
localhost. Then edit pg_hba.conf and add permissions based on the soruce
address of the connection. There are sections in the manual that will
explain the details of what you have to put there.

//Magnus

> -----Original Message-----
> From: Josef Springer [mailto:Josef.Springer@joops.com]
> Sent: Tuesday, September 19, 2006 12:18 PM
> To: Magnus Hagander
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Where is the msi-setup described ?
>
> Hi Magnus,
>
> thanks for quick answer. I have installed PostgreSQL 8.1 on the
> server without the option Accept connections on all addreses, not
> just localhost . I want to connect from a client. How can this
> option be switched on without a new installation of the server ?
>
> Josef
>
> Magnus Hagander wrote:
>
>
>         Hi folks,
>
>
>         where do i get documentation about the msi-setup
> dialogs for
>         Windows plaforms  ?
>
>
>     http://pginstaller.projects.postgresql.org
>
>     //Magnus
>
>
>     ---------------------------(end of broadcast)----------------
> -----------
>     TIP 9: In versions below 8.0, the planner will ignore your
> desire to
>            choose an index scan if your joining column's
> datatypes do not
>            match
>
>
>

Edit postgresql.conf and set a listen_addresses that's not just
localhost. Then edit pg_hba.conf and add permissions based on the soruce
address of the connection. There are sections in the manual that will
explain the details of what you have to put there.

//Magnus

-----Original Message-----
From: Josef Springer [mailto:Josef.Springer@joops.com]
Sent: Tuesday, September 19, 2006 12:18 PM
To: Magnus Hagander
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Where is the msi-setup described ?

Hi Magnus,

thanks for quick answer. I have installed PostgreSQL 8.1 on the
server without the option Accept connections on all addreses, not
just localhost . I want to connect from a client. How can this
option be switched on without a new installation of the server ?

Josef

Magnus Hagander wrote:


		Hi folks,


		where do i get documentation about the msi-setup
dialogs for
		Windows plaforms  ?


	http://pginst
aller.projects.postgresql.org

	//Magnus


	---------------------------(end of broadcast)----------------
-----------
	TIP 9: In versions below 8.0, the planner will ignore your
desire to
	       choose an index scan if your joining column's
datatypes do not
	       match

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

Hi.
To access postgres set pg_hba.conf like this:

host    all     all   0.0.0.0 0.0.0.0 md5

This will allow any user from any IP to connect.
nd: «md5» sets the authentication mode, check the PG documentation for
alternative methods (if you need them).

Cheers,

Andrea


On Tue, 2006-09-19 at 13:00 +0200, Josef Springer wrote:
> Hi Magnus,
>
> i must explain my users how to maintain.
> The menu opens the dialog pgAdminIII - Backend Access Configuration
> Editor with 6 colomns:
> Type
>
> Database
>
> User
>
> IP-Address
>
> Method
>
> Option
>
> host
>
> all
>
> all
>
> 127.0.0.1/32
>
> md5
>
>
>
> host
>
> all
>
> all
>
> ::1/128
>
> md5
>
>
>
>
> Is all required option set ? If no, what is required to access from
> any client ?
>
> Josef
>
> Magnus Hagander wrote:
> > Edit postgresql.conf and set a listen_addresses that's not just
> > localhost. Then edit pg_hba.conf and add permissions based on the soruce
> > address of the connection. There are sections in the manual that will
> > explain the details of what you have to put there.
> >
> > //Magnus
> >
> > > -----Original Message-----
> > > From: Josef Springer [mailto:Josef.Springer@joops.com]
> > > Sent: Tuesday, September 19, 2006 12:18 PM
> > > To: Magnus Hagander
> > > Cc:
> > > Subject: Re: [ADMIN] Where is the msi-setup described ?
> > >
> > > Hi Magnus,
> > >
> > > thanks for quick answer. I have installed PostgreSQL 8.1 on the
> > > server without the option Accept connections on all addreses, not
> > > just localhost . I want to connect from a client. How can this
> > > option be switched on without a new installation of the server ?
> > >
> > > Josef
> > >
> > > Magnus Hagander wrote:
> > >
> > >
> > >         Hi folks,
> > >
> > >
> > >         where do i get documentation about the msi-setup
> > > dialogs for
> > >         Windows plaforms  ?
> > >
> > >
> > >     http://pginst
> > > aller.projects.postgresql.org
> > >
> > >     //Magnus
> > >
> > >
> > >     ---------------------------(end of broadcast)----------------
> > > -----------
> > >     TIP 9: In versions below 8.0, the planner will ignore your
> > > desire to
> > >            choose an index scan if your joining column's
> > > datatypes do not
> > >            match
> > >
> > >
> > >
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Have you searched our list archives?
> >
> >                http://archives.postgresql.org
> >
> >

--
Andrea Gozzi <andrea.gozzi@linuxrevolution.eu>

-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Josef Springer
Sent: Tuesday, September 19, 2006 1:00 PM
To: Magnus Hagander
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Where is the msi-setup described ?

Hi Magnus,

i must explain my users how to maintain.
The menu opens the dialog pgAdminIII - Backend Access Configuration Editor with 6 colomns:

Type	Database	User	IP-Address	Method	Option
host	all	all	127.0.0.1/32	md5
host	all	all	::1/128	md5

Is all required option set ? If no, what is required to access from any client ?
             
Josef      

Hi folks,

i must analyze a customer's database offline. Can i import the databse
of the customer into our PostgreSQL environment ?
What must the customer send us ?
Whats the doings for us to open it in our envioronment ?

Josef

Hi Josef,


> i must analyze a customer's database offline. Can i import the databse
> of the customer into our PostgreSQL environment ?
> What must the customer send us ?
> Whats the doings for us to open it in our envioronment ?

   use pg_dump -o -b -Fc [database to export] > [backup file] in your
customer's side (man pg_dump for details)

   create the database where you'll import the backup and use pg_restore
-v -O -d [database] [backup file] (man pg_restore for details)


--
Arnau

Firstly it would be helpful to say what error you're getting on the
client side.
At a quick guess, I would say it's because you've got 2 "0.0.0.0"
declarations in your pg_hba.conf - you only need the one - like this:

host    all     all     0.0.0.0/0       md5

Regards,

Andy.

Josef Springer wrote:
> Hi folks,
>
> i have a workgroup (not a classic server)  with Windows-XP-machines:
>
> the database server machine contains the line
> host            all            all            0.0.0.0
> 0.0.0.0    md5
> in the file pg_hba.conf
> and
> listen_addresses = '*'
> in the file postgresql.conf.
>
> the 'client's host file contain the line
> */nnn.nnn.nnn.nnn Labor/* where /nnn.nnn.nnn.nnnn/ is the IP-adress of
> the database server machine and /Labor /is the machine's name.
>
> If i start PGAdmin III on the 'client' machine i can not connect to
> the database on the /Labor/ no matter wether i use the machine's name
> or the IP-adress.
>
> What to do ?
>
> mit freundlichen Grüßen / best regards,
> Josef Springer
> (Geschäftsleitung/Management)
>
> Postal
>     Address
>     _Josef.Springer@joops.com _
>     Orlando-di-Lasso Str. 2
>     D-85640 Putzbrunn
> Phone
>     Office
>     +49 (0)89 600 6920
>
>
> Phone
>     Fax
>     +49 (0)89 600 69220
>
>
> Web
>     Web
>     http://www.joops.com
>
>
>
>
> JOOPS
>     *-- the software company --*
>
>
>
>
>
> !DSPAM:37,45a60e36137102078430163!


--
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834

Firstly it would be helpful to say what error you're getting on the client side.
At a quick guess, I would say it's because you've got 2 "0.0.0.0" declarations in your pg_hba.conf - you only need the one - like this:

host    all     all     0.0.0.0/0       md5

Regards,

Andy.

Josef Springer wrote:

Hi folks,

i have a workgroup (not a classic server)  with Windows-XP-machines:

the database server machine contains the line
host            all            all            0.0.0.0        0.0.0.0    md5
in the file pg_hba.conf
and
listen_addresses = '*' in the file postgresql.conf.

the 'client's host file contain the line
*/nnn.nnn.nnn.nnn Labor/* where /nnn.nnn.nnn.nnnn/ is the IP-adress of the database server machine and /Labor /is the machine's name.

If i start PGAdmin III on the 'client' machine i can not connect to the database on the /Labor/ no matter wether i use the machine's name or the IP-adress.

What to do ?

mit freundlichen Grüßen / best regards,
Josef Springer
(Geschäftsleitung/Management)

Postal
    Address
    _Josef.Springer@joops.com _
    Orlando-di-Lasso Str. 2
    D-85640 Putzbrunn
Phone
    Office
    +49 (0)89 600 6920
    
    
Phone
    Fax
    +49 (0)89 600 69220
    
    
Web
    Web
    http://www.joops.com
    
    


JOOPS
    *-- the software company --*


 


!DSPAM:37,45a60e36137102078430163!

"Zum Server ist keine Verbindung möglich,

oder Login/Passwort sind falsch.

Die Anmeldung wurde abgelehnt."
Josef

Andy Shellam (Mailing Lists) wrote:

Firstly it would be helpful to say what error you're getting on the client side.
At a quick guess, I would say it's because you've got 2 "0.0.0.0" declarations in your pg_hba.conf - you only need the one - like this:

host    all     all     0.0.0.0/0       md5

Regards,

Andy.

Josef Springer wrote:

Hi folks,

i have a workgroup (not a classic server)  with Windows-XP-machines:

the database server machine contains the line
host            all            all            0.0.0.0        0.0.0.0    md5
in the file pg_hba.conf
and
listen_addresses = '*' in the file postgresql.conf.

the 'client's host file contain the line
*/nnn.nnn.nnn.nnn Labor/* where /nnn.nnn.nnn.nnnn/ is the IP-adress of the database server machine and /Labor /is the machine's name.

If i start PGAdmin III on the 'client' machine i can not connect to the database on the /Labor/ no matter wether i use the machine's name or the IP-adress.

What to do ?

mit freundlichen Grüßen / best regards,
Josef Springer
(Geschäftsleitung/Management)

Postal
    Address
    _Josef.Springer@joops.com _
    Orlando-di-Lasso Str. 2
    D-85640 Putzbrunn
Phone
    Office
    +49 (0)89 600 6920
    
    
Phone
    Fax
    +49 (0)89 600 69220
    
    
Web
    Web
    http://www.joops.com
    
    


JOOPS
    *-- the software company --*


 


!DSPAM:37,45a60e36137102078430163!

Die Anmeldung wurde abgelehnt."

Please help me. What to do ?

mit freundlichen Grüßen / best regards,
Josef Springer
(Geschäftsleitung/Management)

	Address	Josef.Springer@joops.com	Orlando-di-Lasso Str. 2	D-85640 Putzbrunn
	Office	+49 (0)89 600 6920
	Fax	+49 (0)89 600 69220
	Web	http://www.joops.com

-- the software company --

 

	Address	Josef.Springer@joops.com	Orlando-di-Lasso Str. 2	D-85640 Putzbrunn
	Office	+49 (0)89 600 6920
	Fax	+49 (0)89 600 69220
	Web	http://www.joops.com

-- the software company --

I can understand the exact error as its not in english :) but it seems like an authentication problem. Please change 'md5' to 'trust' in pg_hba.conf file and then use:

pg_ctl -D <path to data folder> reload

That will reload the settings for authentication.

Now once the settings are reloaded try reconnecting to the database and it should go fine this time....

----------------
Shoaib Mir
EnterpriseDB ( www.enterprisedb.com )

On 1/15/07, Josef Springer <Josef.Springer@joops.com > wrote:

Hi folks,

i have a workgroup (not a classic server)  with Windows-XP-machines:

the database server machine contains the line
host   all    all   0.0.0.0   0.0.0.0     md5
in the file pg_hba.conf
and
listen_addresses = '*'
in the file postgresql.conf.

The clients' host file contain the line
nnn.nnn.nnn.nnn Labor where nnn.nnn.nnn.nnnn is the IP-adress of
the database server machine and /Labor /is the machine's name.

If i start PGAdmin III on the 'client' machine i can not connect to
the database on the machine Labor no matter wether i use the machine's name
or the IP-adress. Instead i get the message

"Zum Server ist keine Verbindung möglich,

oder Login/Passwort sind falsch.

Die Anmeldung wurde abgelehnt."

Please help me. What to do ?

mit freundlichen Grüßen / best regards,
Josef Springer
(Geschäftsleitung/Management)

	Address	Josef.Springer@joops.com	Orlando-di-Lasso Str. 2	D-85640 Putzbrunn
	Office	+49 (0)89 600 6920
	Fax	+49 (0)89 600 69220
	Web	http://www.joops.com

-- the software company --

 

You only need to use pg_restore with archives that are not in the
plain-text sql format.  You can just do this:

psql -f <filename> -U OfficeTalk OfficeTalk

to restore.

On Mon, 5 Mar 2007, Josef Springer wrote:

> iI habe dumped a database with
> pg_dump --file="<filename>" -a --schema="OfficeTalk" -h localhost -U
> OfficeTalk "OfficeTalk"
>
> Restoring it with
> pg_restore -d "OfficeTalk" -a -h localhost -U "OfficeTalk" "<filename>"
>
> i get the error
> pg_restore: [archiver] input file does not appear to be a valid archive
>
> What to do ?
>
> mit freundlichen Gr��en / best regards,
> Josef Springer
> (Gesch�ftsleitung/Management)
>
> [Postal]
> Address
> Josef.Springer@joops.com
> Orlando-di-Lasso Str. 2
> D-85640 Putzbrunn
> [Phone]
>
> Office
> +49 (0)89 600 6920
>
>
> [Phone]
>
> Fax
> +49 (0)89 600 69220
>
>
> [Web]
>
> Web
> http://www.joops.com
>
>
>
> [JOOPS]
> -- the software company --
>
>
>
>

--
Jeff Frost, Owner     <jeff@frostconsultingllc.com>
Frost Consulting, LLC     http://www.frostconsultingllc.com/
Phone: 650-780-7908    FAX: 650-649-1954

Josef Springer wrote:
> hello,
>
> we had installed 8.2 and used a database via ADO with the connectstring
> *Driver={PostgreSQL
> Unicode};Server=localhost;Uid=OfficeTalk;Pwd=OfficeTalk;Database=OfficeTalk"
> *
> Now we have installed 8.8 and try to use the database with the same
> connectstring but get the ADO error *80004005.*
There is no PostgreSQL 8.8 - can you tell us what version you are really
using (or, if you think it is 8.8, where you got it from?)

Can you connect to the database with the regular command line tools over
the network (or a GUI tool such as PgAdmin III), or do you get an error
there as well?

The problem may be that it's unable to connect due to a database
configuration issue, not an ADO issue.  If you had a DSN that was
working before, I wouldn't change it until you've verified that you're
actually able to connect to the database properly.

Did you make sure that you made the appropriate changes to
postgresql.conf and pg_hba.conf on the new system to ensure that users
will be able to connect over the network?

--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC  27560
919-463-0999/877-258-8987
http://www.otg-nc.com
Ask me about out VIRTUAL LIVE training options for PostgreSQL - available globally!

• We are using the OLEDB-Provider for ADO.
• On 8.2 the connectionstring works, on 8,4 it does not work.
• The database is local and accessed with localhost.
• An application, whitch acceses the database via an ODBC-driver works. Only ADO does not work. (ADO error *80004005.* )
  

Josef Springer wrote:

hello,

we had installed 8.2 and used a database via ADO with the connectstring
*Driver={PostgreSQL Unicode};Server=localhost;Uid=OfficeTalk;Pwd=OfficeTalk;Database=OfficeTalk"
*
Now we have installed 8.8 and try to use the database with the same connectstring but get the ADO error *80004005.*

There is no PostgreSQL 8.8 - can you tell us what version you are really using (or, if you think it is 8.8, where you got it from?)

Can you connect to the database with the regular command line tools over the network (or a GUI tool such as PgAdmin III), or do you get an error there as well?

The problem may be that it's unable to connect due to a database configuration issue, not an ADO issue.  If you had a DSN that was working before, I wouldn't change it until you've verified that you're actually able to connect to the database properly.

Did you make sure that you made the appropriate changes to postgresql.conf and pg_hba.conf on the new system to ensure that users will be able to connect over the network?

Hi Joserf,

Does your ADO accept a version 8.4 reply from the database. It
may not be supported. In that case, you will need to update your
ADO software.

Cheers,
Ken

On Thu, Mar 25, 2010 at 03:35:10PM +0100, Josef Springer wrote:
> Thanks for quick answer. Sorry, this was a misstype. We are using 8.4 not
> 8.8.
>
>    * We are using the OLEDB-Provider for ADO.
>    * On 8.2 the connectionstring works, on 8,4 it does not work.
>    * The database is local and accessed with localhost.
>    * An application, whitch acceses the database via an ODBC-driver
>      works. Only ADO does not work. (ADO error *80004005.* )
>
> Joserf Springer
>
>
> Chander Ganesan wrote:
>> Josef Springer wrote:
>>> hello,
>>>
>>> we had installed 8.2 and used a database via ADO with the connectstring
>>> *Driver={PostgreSQL
>>> Unicode};Server=localhost;Uid=OfficeTalk;Pwd=OfficeTalk;Database=OfficeTalk"
>>> *
>>> Now we have installed 8.8 and try to use the database with the same
>>> connectstring but get the ADO error *80004005.*
>> There is no PostgreSQL 8.8 - can you tell us what version you are really
>> using (or, if you think it is 8.8, where you got it from?)
>>
>> Can you connect to the database with the regular command line tools over
>> the network (or a GUI tool such as PgAdmin III), or do you get an error
>> there as well?
>>
>> The problem may be that it's unable to connect due to a database
>> configuration issue, not an ADO issue.  If you had a DSN that was working
>> before, I wouldn't change it until you've verified that you're actually
>> able to connect to the database properly.
>>
>> Did you make sure that you made the appropriate changes to postgresql.conf
>> and pg_hba.conf on the new system to ensure that users will be able to
>> connect over the network?
>>
>
>

On Thu, Mar 25, 2010 at 7:35 AM, Josef Springer
<Josef.Springer@joops.com> wrote:
> Thanks for quick answer. Sorry, this was a misstype. We are using 8.4 not
> 8.8.
>
> We are using the OLEDB-Provider for ADO.
> On 8.2 the connectionstring works, on 8,4 it does not work.
> The database is local and accessed with localhost.
> An application, whitch acceses the database via an ODBC-driver works. Only
> ADO does not work. (ADO error *80004005.* )


If you notice the oledb driver is still marked beta and is not
production ready.  It also looks like it was last updated 4 years ago.

http://pgfoundry.org/projects/oledb/

You should probably use the odbc driver since it is production ready
and actively supported.

http://www.postgresql.org/ftp/odbc/versions/msi/

--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

--- On Thu, 25/3/10, Richard Broersma <richard.broersma@gmail.com> wrote:
> wrote:
> > Thanks for quick answer. Sorry, this was a misstype.
> We are using 8.4 not
> > 8.8.
> >
> > We are using the OLEDB-Provider for ADO.
> > On 8.2 the connectionstring works, on 8,4 it does not
> work.
> > The database is local and accessed with localhost.
> > An application, whitch acceses the database via an
> ODBC-driver works. Only
> > ADO does not work. (ADO error *80004005.* )
>
>
> If you notice the oledb driver is still marked beta and is
> not
> production ready.  It also looks like it was last
> updated 4 years ago.
>
> http://pgfoundry.org/projects/oledb/
>
> You should probably use the odbc driver since it is
> production ready
> and actively supported.
>
> http://www.postgresql.org/ftp/odbc/versions/msi/
>


Or try PGNP http://www.pgoledb.com/

mit freundlichen Grüßen / best regards,
Josef Springer
(Geschäftsleitung/Management)

	Address	Josef.Springer@joops.com	Orlando-di-Lasso Str. 2	D-85640 Putzbrunn
	Office	+49 (0)89 600 6920
	Fax	+49 (0)89 600 69220
	Web	http://www.joops.com

(HRB München 86239) -- the software company --

* Josef Springer wrote:

> we are using PostgrSQL 8.1 and the client is connected via ODBC
> PostgreSQL Unicode.
> What must be used to use the install ODBC on a Windows-64 system ?

The latest release of the 32-bit ODBC driver appears to be
<http://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_09_01_0100-1.zip>.

> Is there an ODBC for Windows-64 available and does it work with a
> 32-Bit application ?

With 32-bit applications, use the 32-bit driver.

--
Christian