Re: [ADMIN] Very strange postgresql behaviour
Hi all, Arnau <[EMAIL PROTECTED]> writes: I don't know, we have discovered those two rows but I'm not sure if there are more. Is there any way to check it? Update and see if the problem is gone ... We have done: update customer_app_config set customer_app_config_id = customer_app_config_id And the problem has gone. Thank you very much!!! -- Arnau ---(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
[ADMIN] postgres-two different version
Hi all Probably is a stupid question, But I m a newbie and I dont want to destroy my server :-) Is possible to install two different version of postgresql on the same Linux server? I want to install the 8.2 version in a server where is installed 8.1.3 version If the answer is affirmative,I think that I have to change 2 things :the installation directory and the port. 1) I install postgres with the rpm command .I think that I have to use the option relocate.But how? 2) In whats file I can change the port? Thanks a lot. Gian Piero Bottini __ dott. Gian Piero Bottini ARPA Valle d'Aosta Loc. Grande Charrière 44 11020 Saint Christophe - Aosta Tel. 0165-278552 contatto skype gianpiero.bottini ___
Re: [ADMIN] postgres-two different version
Am 30.01.2007, 12:46 Uhr, schrieb Bottini <[EMAIL PROTECTED]>: Hi all Probably is a stupid question, But I ‘m a newbie and I don’t want to destroy my server :-) Is possible to install two different version of postgresql on the same Linux server? I want to install the 8.2 version in a server where is installed 8.1.3 version If the answer is affirmative,I think that I have to change 2 things :the installation directory and the port. 1) I install postgres with the rpm command .I think that I have to use the option –relocate.But how? 2) In what’s file I can change the port? Thanks a lot. Gian Piero Bottini __ dott. Gian Piero Bottini ARPA Valle d'Aosta Loc. Grande Charrière 44 11020 Saint Christophe - Aosta Tel. 0165-278552 contatto skype gianpiero.bottini ___ I think it should be possible to run 2 pg-servers on the same machine. They must use different datastores and listen to different ports. You can change the port in the postgresql.conf-file in the datastore. bye Uwe Seher _ ingenieurbüro kauppert nebeniusstr. 34 d-76137 karlsruhe fon +49 721 3548969-3 fax +49 721 3548969-5 email [EMAIL PROTECTED] web www.ib-kauppert.de _ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] postgres-two different version
"Bottini" <[EMAIL PROTECTED]> writes: > Is possible to install two different version of postgresql on the same > Linux server? I want to install the 8.2 version in a server where is > installed 8.1.3 version You can, but not when installing from RPM: the RPMs have a fixed idea of where to put the software, and I don't think it's feasible to change. You'd need to build from source and use the --prefix configure option to put the two sets of code in different places. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [ADMIN] postgres-two different version
Why would you want two servers on the same box ??? There's this thing called "schemas" within one database... and postgreSQL is very capable of managing multiple databases from the same server If you insist on trying to run two postgreSQL server on teh same box -- You also need to make sure that your two different versions dopnt share TCP/IP ports -- they cannot both listen on the same IP:PORT address -- so you will need to manage your postgresql.conf and pg_hba.conf files separately -- one for each postgresql server... ditto for your startup scripts. You will probably also have some issues when using pgsql at the command line [localhost]. Why not just upgrade your 8.1.3 installation to 8.2 ? "Tom Lane" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > "Bottini" <[EMAIL PROTECTED]> writes: >> Is possible to install two different version of postgresql on the same >> Linux server? I want to install the 8.2 version in a server where is >> installed 8.1.3 version > > You can, but not when installing from RPM: the RPMs have a fixed idea of > where to put the software, and I don't think it's feasible to change. > You'd need to build from source and use the --prefix configure option > to put the two sets of code in different places. > > regards, tom lane > > ---(end of broadcast)--- > TIP 6: explain analyze is your friend > ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [ADMIN] Terminating a query that appears to be hung
and from the shell prompt: you can find ALL postgreSQL process id's by: %>ps ax | grep postgres ""Eduardo J. Ortega"" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > You can also kill the postgres process corresponding to the hung query. do > NOT > kill -9. Only kill. Postgres will rollback any uncomitted transaction and > finish that connection gracefully. > > On Monday 29 January 2007 18:35, Phillip Smith wrote: >> Can youo be a bit more specific...? What client? >> >> Psql should terminate the connection when it exist. pgAdmin will close it >> when you exit the ap, or if you choose 'Disconnect' from the menu. In PHP >> you'll need to call pg_close function... Every 'client' will have a >> different method... >> >> -Original Message- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Robert D Oden >> Sent: Tuesday, 30 January 2007 2:03 AM >> To: PgSQL ADMIN >> Subject: [ADMIN] Terminating a query that appears to be hung >> >> Is there a way to terminate a client session without having to restart >> Postgres. >> >> Thanks > > -- > Eduardo J. Ortega - Linux user #222873 > "No fake - I'm a big fan of konqueror, and I use it for everything." -- > Linus > Torvalds > > ---(end of broadcast)--- > TIP 5: don't forget to increase your free space map settings > ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [ADMIN] Postgres encyrption export
On Mon, Jan 29, 2007 at 12:01:26 -0500, Tom Dong <[EMAIL PROTECTED]> wrote: > > We are wondering whether there has been US Commerce Department review of > the Postgres application for export. Specifically, we understand > Postgres contains encryption capabilities, and we would like to include > the application with our products delivered outside the US. Can you let > me know whether that review has occurred, and if so, the result? If you > have not had a review, know of any companies that have? Isn't there an exception for cases where the source is published? ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] Postgres encyrption export
Not really. The review process is more like disclosure than control. For shipping oversea, any products involving encryption must disclose the encryption features/capabilities. Commercial products usually have already gone through this process by the vendors, namely disclosed to the government. Products that include commercial encryption libraries can usually quote the ECCN (some export permission number) of these commercial products. We are currently looking for any information regarding to the ECCN or other export review information of postgres. Thanks! tom -Original Message- From: Bruno Wolff III [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 30, 2007 2:08 PM To: Tom Dong Cc: pgsql-admin@postgresql.org Subject: Re: Postgres encyrption export On Mon, Jan 29, 2007 at 12:01:26 -0500, Tom Dong <[EMAIL PROTECTED]> wrote: > > We are wondering whether there has been US Commerce Department review of > the Postgres application for export. Specifically, we understand > Postgres contains encryption capabilities, and we would like to include > the application with our products delivered outside the US. Can you let > me know whether that review has occurred, and if so, the result? If you > have not had a review, know of any companies that have? Isn't there an exception for cases where the source is published? ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] postgres-two different version
We run two servers when we are trying out new versions (development, qa, and production). And, its a failsafe for upgrades. Since you need to unload for major upgrades anyway, it is completely reasonable. Naomi codeWarrior wrote: > Why would you want two servers on the same box ??? There's this thing called > "schemas" within one database... and postgreSQL is very capable of managing > multiple databases from the same server > > If you insist on trying to run two postgreSQL server on teh same box -- You > also need to make sure that your two different versions dopnt share TCP/IP > ports -- they cannot both listen on the same IP:PORT address -- so you will > need to manage your postgresql.conf and pg_hba.conf files separately -- one > for each postgresql server... ditto for your startup scripts. > > You will probably also have some issues when using pgsql at the command line > [localhost]. > > Why not just upgrade your 8.1.3 installation to 8.2 ? > > > > > "Tom Lane" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > >> "Bottini" <[EMAIL PROTECTED]> writes: >> >>> Is possible to install two different version of postgresql on the same >>> Linux server? I want to install the 8.2 version in a server where is >>> installed 8.1.3 version >>> >> You can, but not when installing from RPM: the RPMs have a fixed idea of >> where to put the software, and I don't think it's feasible to change. >> You'd need to build from source and use the --prefix configure option >> to put the two sets of code in different places. >> >> regards, tom lane >> >> ---(end of broadcast)--- >> TIP 6: explain analyze is your friend >> >> > > > > ---(end of broadcast)--- > TIP 5: don't forget to increase your free space map settings > -- Naomi Walker Chief Information Officer Mphasis Healthcare Solutions [EMAIL PROTECTED] ---An EDS Company 602-604-3100 A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort. --Herm Albright (1876 - 1944) -- CONFIDENTIALITY NOTICE -- Information transmitted by this e-mail is proprietary to MphasiS and/or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this e-mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at [EMAIL PROTECTED] and delete this mail from your records.
Re: [ADMIN] Postgres encyrption export
Tom Dong wrote: > We are wondering whether there has been US Commerce Department review > of the Postgres application for export. The Debian project submits all software it distributes to said department, so one can be fairly assured that they have heard of PostgreSQL, but how that affects what you are distributing I'm not sure. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] Postgres encyrption export
I am still searching for information on the internet about Postgres Export review by US Commerce department. I did see an early email posted on POstgres mailing list about ECCN number of Postgres and saw the response debating if Postgres should be considered a US product. But I did not see any conclusion to that question, namely if POstgres has an ECCN number and if Postgres is a US product. Thanks! tom -Original Message- From: Peter Eisentraut [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 30, 2007 4:03 PM To: pgsql-admin@postgresql.org Cc: Tom Dong Subject: Re: [ADMIN] Postgres encyrption export Tom Dong wrote: > We are wondering whether there has been US Commerce Department review > of the Postgres application for export. The Debian project submits all software it distributes to said department, so one can be fairly assured that they have heard of PostgreSQL, but how that affects what you are distributing I'm not sure. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [ADMIN] Postgres encyrption export
Tom Dong wrote: > I am still searching for information on the internet about Postgres > Export review by US Commerce department. > > I did see an early email posted on POstgres mailing list about ECCN > number of Postgres and saw the response debating if Postgres should be > considered a US product. But I did not see any conclusion to that > question, namely if POstgres has an ECCN number and if Postgres is a US > product. I have not seen any activity on that topic for years, so my guess is that nothing has been researched in that area. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [ADMIN] pg_dumpall problems
I should be a little more specific. The way we currently do backups is that
this backup user dumps user/group data (i.e. the --globals-only flag) for
pg_dumpall, and we pg_dump individual databases.
We grant read access to this backup user for all non-system
tables/views/etc. (and usage for non-system schemas) in user databases so it
can read and dump the data. We also grant it read access on select system
tables to make pg_dumpall work. We do this for two reasons. First, we like
to follow the generally good security practice of minimum access, and
second, (as a result of the first), we don't want to tickle a bug in our
backup system that magically corrupts our data (which is possible if this
user has more than read access).
So, is there any remedy to my problem (see below) short of granting
superuser access? Is this a bug (which I would then report on the
appropriate channels)?
As for Tom's suggestion, there's no way to specify the database in
pg_dumpall, only the server, and the same bug occurs if I run as the user on
the same server and cluster with the same major version.
Peter
On 1/29/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Peter Koczan" <[EMAIL PROTECTED]> writes:
> Right now, we run pg_dumpall as a non-superuser,
[ raised eyebrow... ] That's never been a recommended procedure.
> The weird thing is, whenever I run this exact same command from psql as
the
> backup user, it works.
Maybe you're not trying it in the same database pg_dumpall is?
regards, tom lane
Original post for all those to see:
-
Thanks for your help thus far. I almost have 8.2 ready (hooray no more
ancient 7.4). I do have one more problem which is likely the last thing
before pushing out live support. pg_dumpall isn't working.
Right now, we run pg_dumpall as a non-superuser, let's call it backup, whom
we give read access to the appropriate system tables (pg_shadow in 7.4,
pg_authid in 8.2), I get this error...
pg_dumpall: query failed: ERROR: permission denied for relation pg_authid
pg_dumpall: query was: SELECT rolname, rolsuper, rolinherit, rolcreaterole,
rolcreatedb, rolcatupdate, rolcanlogin, rolconnlimit, rolpassword,
rolvaliduntil, pg_catalog.shobj_description(oid, 'pg_authid') as rolcomment
FROM pg_authid ORDER BY 1
The weird thing is, whenever I run this exact same command from psql as the
backup user, it works.
template1=> select current_role;
current_user
--
backup
(1 row)
template1=> \z pg_catalog.pg_authid;
Access privileges for database "template1"
Schema | Name| Type | Access privileges
+---+---+--
pg_catalog | pg_authid | table |
{postgres=arwdxt/postgres,backup=r/postgres}
template1=> SELECT rolname, rolsuper, rolinherit, rolcreaterole,
rolcreatedb, rolcatupdate, rolcanlogin, rolconnlimit, rolpassword,
rolvaliduntil, pg_catalog.shobj_description(oid, 'pg_authid') as rolcomment
FROM pg_authid ORDER BY 1;
template1=> SELECT rolname, rolsuper, rolinherit, rolcreaterole,
rolcreatedb, rolcatupdate, rolcanlogin, rolconnlimit, rolpassword,
rolvaliduntil, pg_catalog.shobj_description(oid, 'pg_authid') as rolcomment
FROM pg_authid ORDER BY 1;
(There's data...glorious, glorious data).
The easy solution is to make backup a database superuser, but that's a
change I'd not like to make right now since I don't understand all the
security implications. What's the deal with this error, and is there any
nicer solution? Thanks much in advance.
Re: [ADMIN] pg_dumpall problems
"Peter Koczan" <[EMAIL PROTECTED]> writes: > So, is there any remedy to my problem (see below) short of granting > superuser access? Is this a bug (which I would then report on the > appropriate channels)? It's not a bug. > As for Tom's suggestion, there's no way to specify the database in > pg_dumpall, only the server, and the same bug occurs if I run as the user on > the same server and cluster with the same major version. You still haven't responded to my query: did you try it in the same database that pg_dumpall is connecting to? My guess is that you have munged the permissions on pg_shadow or pg_authid without understanding that that will only take effect in the one database you do it in. pg_dumpall is connecting to either "postgres" or "template1" depending on version; what's the permissions situation in that database? regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[ADMIN] Cannot initdb for 8.2.1 - "..../postgres.bki" does not exist
Hello, I'm trying to install and init 8.2.1 on a FreeBSD 6.2 server. It used to run 8.1.4 no problem. I uninstalled 8.1, renamed /usr/local/pgsql in case I ever need it (I'm not really bothered about preserving the data) and built 8.2.1 - all fine. But when I try to initdb: --- [EMAIL PROTECTED]> su -l pgsql [EMAIL PROTECTED]> /usr/local/bin/initdb -D /usr/local/pgsql/data -E UNICODE initdb: file "/usr/local/share/postgresql/postgres.bki" does not exist This means you have a corrupted installation or identified the wrong directory with the invocation option -L. --- Tried adding " -L /usr/local/share/postgresql/" (and removing -E) but no joy. The .../share/postgresql/ files do exist. Not sure why this is happening now, it's never happened before. I've got a horrible feeling it's something embarrassingly simple but I'm stumped. And clues? Many thanks --- Simon Kinsella This message has been scanned for viruses. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] Cannot initdb for 8.2.1 - "..../postgres.bki" does not exist
On Wed, 2007-01-31 at 01:27 +, Simon Kinsella wrote: > Hello, > > I'm trying to install and init 8.2.1 on a FreeBSD 6.2 server. It used to run > 8.1.4 no problem. I uninstalled 8.1, renamed /usr/local/pgsql in case I > ever need it (I'm not really bothered about preserving the data) and built > 8.2.1 - all fine. > > But when I try to initdb: > > --- > [EMAIL PROTECTED]> su -l pgsql > [EMAIL PROTECTED]> /usr/local/bin/initdb -D /usr/local/pgsql/data -E UNICODE > initdb: file "/usr/local/share/postgresql/postgres.bki" does not exist > This means you have a corrupted installation or identified > the wrong directory with the invocation option -L. I'm go gonna out on a limb here and guess that the files postgresql is trying to initdb with are 8.1 and not 8.2 version files. ---(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
Re: [ADMIN] Cannot initdb for 8.2.1 - "..../postgres.bki" does not exist
"Simon Kinsella" <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED]> /usr/local/bin/initdb -D /usr/local/pgsql/data -E UNICODE > initdb: file "/usr/local/share/postgresql/postgres.bki" does not exist > This means you have a corrupted installation or identified > the wrong directory with the invocation option -L. > The .../share/postgresql/ files do exist. Looking at the code, this message is emitted if attempting to stat() the file fails, regardless of what the actual errno is. So I'm wondering about permissions problems, specifically inability to search one of the directories on the path. We should adjust initdb to report the actual kernel errno value, instead of presuming that it's "file not found". regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] Postgres encyrption export
Am Dienstag, 30. Januar 2007 23:03 schrieb Tom Dong: > I did see an early email posted on POstgres mailing list about ECCN > number of Postgres and saw the response debating if Postgres should be > considered a US product. According to the lawyers I'm involved with, the contributions by US citizens or residents are certainly significant enought to make this true for the purpose of export or embargo control. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
