Re: [BUGS] BUG #5789: asking password
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Reegun Richard.J wrote: > while installing,next to the step of data directory it asks for password to > continue ,i cant install I m assuming --you r trying to install first time --PPSS/PG installer on Win Xp , at the time of installing --it is going to ask you Postgres password , pls remember it is going to create 2 Postgres User, one is OS and another is Database User i.e SuperUser. when you have provided the password ? what the Error message you are getting ? - -- regards, tushar Lead QA Engineer EnterpriseDB Corporation The Enterprise Postgres Company www.enterprisedb.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFNBd0vfQNodY2PIRoRAgluAJ9ayut8btfdAmdvrf68gPvMgRQWNQCfbnYd XSpQb1UwkqOeoBAaDij7uu4= =uTWl -END PGP SIGNATURE- -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] variadic flag doesn't work with "any" type
On Fri, Dec 10, 2010 at 2:44 PM, Pavel Stehule wrote: > 2010/12/10 Tom Lane : >> Pavel Stehule writes: >>> 2010/12/9 Tom Lane : What exactly is the use-case for that? >> >>> I am working on function that can help with record updating. It's >>> based on polymorphic types. I would to allow a multiple modification >>> per one call - like UPDATE statement does. >>> some like: >>> record_set_fields(anyelement, key text, value "any" [, key text, value >>> "any" [..]]) returns anyelement >> >> OK, makes sense, since you don't want to constrain the values to be all >> the same datatype. > > ok, can I send a patch? In the part of Tom's email you didn't quote, he wrote "this can't work". Did you miss that part? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Problems with max_connections parameter
Hi again Have something else I can do to reach the limit of the parameter max_connections? This may be a bug? Thanks Jorge On Mon, Dec 6, 2010 at 1:31 PM, Tom Lane wrote: > Jorge Augusto Meira writes: >> The error message was: >> "Erro Conexão: A tentativa de conexão falhou." >> or >> "Erro Conexão: FATAL: connection limit exceeded for non-superusers" > > Hmm ... I can't find the first of those anywhere in the 8.4 message > lists; but the second one definitely says that you *are* hitting the > max_connections limit, whether you think you should be or not. > > I wonder whether you are neglecting to allow for the fact that backends > have a nonzero shutdown time? If you disconnect and immediately > reconnect, it's possible that your old backend is still around, so that > the new connection attempt causes max_connections to be exceeded. This > is particularly likely if the test program is on the same machine as the > database server, because the test program itself is likely to have a > higher scheduling priority than the old backend. > > regards, tom lane > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
