Re: [BUGS] Bug in CREATE FUNCTION with character type
Hello, Tom. You wrote: TL> Pavel Golub writes: >> Example: >> CREATE OR REPLACE FUNCTION test_char_function() >> RETURNS TABLE(id int, salesourcecode character) AS >> $BODY$ >> VALUES (1, 'one'), (2, 'two'), (3, 'three'); >> $BODY$ >> LANGUAGE 'sql' >> pqfmod function from libpq library for salesourcecode column returns >> 0, which is wrong. Who can ever imagine bpchar of length 0? :) TL> I get -1 (indicating unspecified), which is what I'd expect. You TL> sure about the zero? TL> regards, tom lane My fault. Yes, of course, it's -1 -- With best wishes, Pavel mailto:pa...@gf.microolap.com -- 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 #5422: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initinot initiate the connecti
The following bug has been logged online: Bug reference: 5422 Logged by: Alex Soto Paez Email address: alejandro.soto...@gmail.com PostgreSQL version: 8.4 Operating system: linux Description:problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initinot initiate the connecti Details: The PostgreSQL server failed to start. Please check the log output: 2010-04-14 18:48:24 CDT FATAL: could not lock file >: no such file? directory [Fail] problems installing postgresql-8.4 deleted folder / var / run / postgresql / .s.PGSQL.lock not initiate the connection to port 5432 -- 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 #5423: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initiate the connecti
The following bug has been logged online: Bug reference: 5423 Logged by: Alex Soto Paez Email address: alejandro.soto...@gmail.com PostgreSQL version: 8.4 Operating system: linux 9.10 Description:problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initiate the connecti Details: problems installing postgresql-8.4 deleted folder / var / run / postgresql / .s.PGSQL.lock not initiate the connection to port 5432 when installing postgresql-8.4 is installed correctly while running the command: $ Service postgresql-8.4 status Published online defautl port 5432, but at reboot the machine no longer seems in line appears down and restart the server payable are parachute with the error: $sudo /ect/init.d/postgresql-8.4 restart The PostgreSQL server failed to start. Please check the log output: 2010-04-14 18:48:24 CDT FATAL: could not lock file >: no such file? directory [Fail] run and hand it to guide the pid file and everything goes well but when you see another restart the computer I get the same error described above. not save the folder with the Pid and does not connect to port 5432 Someone can help me In advance thank you very much. -- 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] BUG #5416: int4inc() is wrong
Hi Tom, > If you can show me rewrites of all the basic arithmetic operations that > detect overflow in full compliance with the C standard, and are > readable, portable, and efficient, I'm all ears. These are the best ones that I know of: https://www.securecoding.cert.org/confluence/display/seccode/INT32-C.+Ensure+that+operations+on+signed+integers+do+not+result+in+overflow Even if you dislike these, please take a look at the safety checks for shifts. The current postgresql shift functions need to be strengthened, and it is easy to do. John Regehr -- 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] build error: strlcat/strlcpy used from heimdal libroken.so
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Bruce, On 15.04.2010 03:59, Bruce Momjian wrote: > I haven't seen anyone reply to this report, Probably because Craig Ringer forwarded it to the -hackers list with cc to me personally, but not to these lists. For that thread see http://thread.gmane.org/gmane.comp.db.postgresql.devel.general/139424 > which might mean we are > waiting for Gentoo to be fixed. Gentoo is notoriously dynamic and it is > hard for us to adjust based on their changes in every case, which I > guess explains why 8.4.X has not been fixed either. As I see it, Gentoo is one of the best ways to expose bugs in the build system of any package, due to the high number of from-source builds using various setups that Gentoo users perform. So I'd not say you'd be adjusting pgsql to Gentoo, but you'd be fixing a bug in your build system which Gentoo users have found and analyzed, but which might as well hit other people building from source on their own. So yes, Gentoo could address this at the distribution level, and as I wrote on the Gentoo bug report, I hope they will do so soon. But the bug is in the pgsql build system (and a bit in heimdal), so if you were to apply one of the proposed fixes upstream, at least for future releases, then more users could benefit. > Martin von Gagern wrote: >> Another alternative might be choosing behaviour based on the detection >> of suitable function declarations, i.e. HAVE_DECL_STRLCAT instead of >> HAVE_STRLCAT. Or you might try enabling the -Wl,--as-needed flag before >> detecting these library functions, to ensure the same behaviour at >> configure time and at build time. In both cases you might whish to >> rename those symbols in case you use your own implementation, just to >> make sure the linker knows which one to choose. I've thought of one more alternative: Move the detection of gssapi and krb5 libraries to a place after strcat/strcpy have been detected. Greetings, Martin -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvGtE0ACgkQRhp6o4m9dFvLqwCgmszpmy54y7oTxxNT6ssmTps+ J5IAoI9ENyPBVtZVsgSOfGPA1I3s/Wbl =jpbU -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] BUG #5423: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initiate the connecti
On Wed, Apr 14, 2010 at 8:15 PM, Alex Soto Paez wrote: > > The following bug has been logged online: > > Bug reference: 5423 > Logged by: Alex Soto Paez > Email address: alejandro.soto...@gmail.com > PostgreSQL version: 8.4 > Operating system: linux 9.10 > Description:problems installing postgresql-8.4 deleted folder / > .s.PGSQL.lock not initiate the connecti > Details: > > problems installing postgresql-8.4 deleted folder / var / run / postgresql > / > .s.PGSQL.lock not initiate the connection to port 5432 > > when installing postgresql-8.4 is installed correctly while running the > command: > > $ Service postgresql-8.4 status > > Published online defautl port 5432, but at reboot the machine no longer > seems in line appears down and restart the server payable are parachute > with > the error: > > > $sudo /ect/init.d/postgresql-8.4 restart > > The PostgreSQL server failed to start. Please check the log output: > 2010-04-14 18:48:24 CDT FATAL: could not lock file postgresql > / .s.PGSQL.lock>>: no such file? directory > > > [Fail] > > run and hand it to guide the pid file and everything goes well but when you > see another restart the computer I get the same error described above. not > save the folder with the Pid and does not connect to port 5432 > > Someone can help me > > In advance thank you very much. > > Does the '/var/run/postgresql' directory exist and is it writeable by the postgres user? If it is not, I would say it's a bug for the packager of this install of postgres. Typically, postgres puts its lock / sockets in '/tmp'. You say linux, but don't say which linux, by your version string (9.10) I'm guessing that this is ubuntu? --Scott > -- > 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] BUG #5418: psql exits after using tab-completion with error message
Ben Madin writes: > I also reported it to Apple, but without this information, so I hope they get > the sense that it might be important enough to look at, especially if there > is already a fix known. Mine is problem ID 7866382, if you'd like to add a note to yours pointing out the duplication. If this is biting you on a regular basis, one easy workaround would be to add a dummy table or index to change the number of possible completions. 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
Re: [BUGS] Bug in CREATE FUNCTION with character type (CONFIRMED BUG)
Pavel Stehule writes: > I think, so RETURNS TABLE can be modified for returning typmode > without significant problems - this function is called in table > context and I don't see any problematic use case. RETURNS TABLE is just a shorthand for some OUT parameters. I don't believe it's either easy or a good idea to make it work differently from every other function-argument-or-result case. 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
Re: [BUGS] Reset ACL to default for pg 8.0
Thanks Bruce for replying.
The ACL is display in the PgAdmin tool for Windows on the properties for a
table or function. ACL is the Privileges. By default, when you create a new
function or table, the ACL is null. However, if you add some privileges, and
then remove all, the ACL is not longer null, it displays the brackets {}.
I just need to know if the brackets are normal when all the privileges are
remove. Or how to reset the privileges (ACL) to default (null).
Thanks,
Juan C. Aragon
From: pgsql-bugs-ow...@postgresql.org
[mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Bruce Momjian
Sent: Wednesday, April 14, 2010 10:13 PM
To: Juan C. Aragon
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Reset ACL to default for pg 8.0
Juan C. Aragon wrote:
> Hi Guys:
>
>
>
> I need to know how to reset the ACL to default (null) for a function. This
> is for PostgreSQL 8.0.14 and 8.4.1 on Windows.
>
> I used the User Interface to removed all the Privileges, but the ACL is
> still = {}
>
> I need to make the ACL to be blank (null), nothing in there.
>
>
>
> Because if the ACL = {} and I do a db restore, it sets the ACL = ,
> but I need it to be blank.
Well, if I create a table and look at pg_dump, I see:
ALTER TABLE public.test OWNER TO postgres;
and the owner has permissions by default on the table. Perhaps you want
to revoke owner permissions on the table.
Where are you seeing this ACL?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
--
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] Bug in CREATE FUNCTION with character type (CONFIRMED BUG)
2010/4/15 Tom Lane :
> Pavel Stehule writes:
>> I think, so RETURNS TABLE can be modified for returning typmode
>> without significant problems - this function is called in table
>> context and I don't see any problematic use case.
>
> RETURNS TABLE is just a shorthand for some OUT parameters. I don't
> believe it's either easy or a good idea to make it work differently
> from every other function-argument-or-result case.
>
I don't know now. It minimally have to be documented
foodmart=# create function f() returns table (a varchar(10), b
varchar(20)) as $$values('Pavel','Stehule')$$ language sql;
CREATE FUNCTION
Time: 121,506 ms
foodmart=# select * from f();
a |b
---+-
Pavel | Stehule
(1 row)
Time: 0,718 ms
foodmart=# create table x as select * from f();
SELECT
Time: 105,357 ms
foodmart=# \d x
Table "public.x"
Column | Type| Modifiers
+---+---
a | character varying |
b | character varying |
workaround is relative simple
foodmart=# create function f() returns table (a varchar(10), b
varchar(20)) as $$values('Pavel','Stehule')$$ language sql;
CREATE FUNCTION
Time: 1,009 ms
foodmart=# create table x as select a::varchar(20), b::varchar(20)
from (select * from f()) x ;
SELECT
Time: 48,592 ms
foodmart=# \d x
Table "public.x"
Column | Type | Modifiers
+---+---
a | character varying(20) |
b | character varying(20) |
Regards
Pavel Stehule
> 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
[BUGS] BUG #5424: Not able to Install
The following bug has been logged online: Bug reference: 5424 Logged by: Aditya Vats Email address: aditya.v...@cerner.com PostgreSQL version: 8.4.2-1 Operating system: Windows Vista Description:Not able to Install Details: While installing I am getting an error saying : The password specified was incorrect.Please enter the correct password for the postgress windows user account. -- 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] BUG #5422: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initinot initiate the connecti
Alex Soto Paez escribió: > > The following bug has been logged online: > > Bug reference: 5422 > Logged by: Alex Soto Paez > Email address: alejandro.soto...@gmail.com > PostgreSQL version: 8.4 > Operating system: linux > Description:problems installing postgresql-8.4 deleted folder / > .s.PGSQL.lock not initinot initiate the connecti > Details: This is not a bug, is a duplicate of #5423, and is being discussed in the spanish list. Thanks. -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- 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] BUG #5418: psql exits after using tab-completion with error message
Thanks Tom, I also reported it to Apple, but without this information, so I hope they get the sense that it might be important enough to look at, especially if there is already a fix known. I also contacted William Kyngesbury, and he was sympathetic (but had never had the problem himself, but neither does he use the tab-completion), but would rather Apple fixed it because his GIS software suite is very based on using Apple OSX frameworks where they exist. cheers Ben On 15/04/2010, at 12:13 , Tom Lane wrote: > I wrote: >> It's fairly easy to reproduce in the regression database: >> type "\d ten". I'm not sure what the triggering condition >> is exactly, because some seemingly-similar cases don't fail, >> for instance "\d test" works as expected, ditto "\d t". > > It turns out that the problem occurs when there are exactly 9 + 10*N > possible completions, for any N>=0. There's an off-by-one logic bug > in libedit that results in a memory stomp because it forgets to enlarge > an array before storing a terminating null pointer in it. > > The upstream netbsd sources incorporated a fix some time ago: > http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libedit/readline.c.diff?r1=1.82&r2=1.83&sortby=date&f=h > with credit to Caleb Welton at Greenplum --- I wonder if he found it > because of psql failing? Apple hasn't incorporated this fix as of > OS X 10.6.3, however. > > What's slightly more distressing is that the same source file > (readline.c) appears to have at least two other occurrences of the same > broken array-enlargement coding pattern, which were *not* fixed. > > I've reported this to Apple but I'm not real sure where to file NetBSD > bugs. Anybody want to yank the BSD guys' chain about the other errors? > > regards, tom lane -- Ben Madin AusVet Animal Health Services P.O. Box 5467 Broome WA 6725 Australia t : +61 8 9192 5455 f : +61 8 9192 5535 m : 0448 887 220 e : b...@ausvet.com.au AusVet's website: http://www.ausvet.com.au This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this email are the opinion of the writer only and are not endorsed by AusVet Animal Health Services unless expressly stated otherwise. Although AusVet uses virus scanning software we do not accept liability for viruses or similar in any attachments. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] Dump and Restore in postgresql-8.3.6-1PGDG
I am on Linux using postgresql-8.3.6-1PGDG Taking Dump using = export PGPASSWORD=suresha && pg_dump -b -c -C --format=c -h localhost -p 5432 -U suresha -f /tmp/dump/db/suresha.sql suresha Trying to Restore the same like === [r...@cu018 scripts]# pg_restore -c --format=c -h localhost -p 5432 -U suresha -d suresha /tmp/dump/db/suresha.sql Password: pg_restore: [archiver (db)] Error while PROCESSING TOC: pg_restore: [archiver (db)] Error from TOC entry 6; 2615 2200 SCHEMA public postgres pg_restore: [archiver (db)] could not execute query: ERROR: must be owner of schema public Command was: DROP SCHEMA public; pg_restore: [archiver (db)] could not execute query: ERROR: schema "public" already exists Command was: CREATE SCHEMA public; pg_restore: [archiver (db)] Error from TOC entry 2663; 0 0 COMMENT SCHEMA public postgres pg_restore: [archiver (db)] could not execute query: ERROR: must be owner of schema public Command was: COMMENT ON SCHEMA public IS 'standard public schema'; pg_restore: WARNING: no privileges could be revoked for "public" pg_restore: WARNING: no privileges could be revoked for "public" pg_restore: WARNING: no privileges were granted for "public" pg_restore: WARNING: no privileges were granted for "public" WARNING: errors ignored on restore: 3 Wondering how can I suppress the Error and other messages seen above. Thanks SureshA
Re: [BUGS] Dump and Restore in postgresql-8.3.6-1PGDG
On Thu, Apr 15, 2010 at 12:47 PM, Scott Mead wrote: > On Thu, Apr 15, 2010 at 10:33 AM, suresh adapa wrote: > >> >> >> I am on Linux using postgresql-8.3.6-1PGDG >> >> >> >> Taking Dump using >> >> = >> >> export PGPASSWORD=suresha && pg_dump -b -c -C --format=c -h localhost -p >> 5432 -U suresha -f /tmp/dump/db/suresha.sql suresha >> >> >> >> Trying to Restore the same like >> >> === >> >> [r...@cu018 scripts]# pg_restore -c --format=c -h localhost -p 5432 -U >> suresha -d suresha /tmp/dump/db/suresha.sql >> >> Password: >> >> pg_restore: [archiver (db)] Error while PROCESSING TOC: >> >> pg_restore: [archiver (db)] Error from TOC entry 6; 2615 2200 SCHEMA >> public postgres >> >> pg_restore: [archiver (db)] could not execute query: ERROR: must be owner >> of schema public >> >> Command was: DROP SCHEMA public; >> >> pg_restore: [archiver (db)] could not execute query: ERROR: schema >> "public" already exists >> >> Command was: CREATE SCHEMA public; >> >> pg_restore: [archiver (db)] Error from TOC entry 2663; 0 0 COMMENT SCHEMA >> public postgres >> >> pg_restore: [archiver (db)] could not execute query: ERROR: must be owner >> of schema public >> >> Command was: COMMENT ON SCHEMA public IS 'standard public schema'; >> >> pg_restore: WARNING: no privileges could be revoked for "public" >> >> pg_restore: WARNING: no privileges could be revoked for "public" >> >> pg_restore: WARNING: no privileges were granted for "public" >> >> pg_restore: WARNING: no privileges were granted for "public" >> >> WARNING: errors ignored on restore: 3 >> >> >> >> Wondering how can I suppress the Error and other messages seen above. >> > > > This is because you're restoring into the same database that you backed up > from. I recommend creating a new database 'suresha_new' > > Then, restore into that new database. Once you've restored, you can: > > > ALTER DATABASE suresha RENAME TO suresha_orig; > > ALTER DATABASE suresha_new RENAME TO suresha; > > --Scott > BTW -- THis is not a bug, you should have posted to the -general or -admin list, not the -bugs list. --Scott > >> >> >> >> Thanks >> >> SureshA >> > >
Re: [BUGS] Dump and Restore in postgresql-8.3.6-1PGDG
On Thu, Apr 15, 2010 at 10:33 AM, suresh adapa wrote: > > > I am on Linux using postgresql-8.3.6-1PGDG > > > > Taking Dump using > > = > > export PGPASSWORD=suresha && pg_dump -b -c -C --format=c -h localhost -p > 5432 -U suresha -f /tmp/dump/db/suresha.sql suresha > > > > Trying to Restore the same like > > === > > [r...@cu018 scripts]# pg_restore -c --format=c -h localhost -p 5432 -U > suresha -d suresha /tmp/dump/db/suresha.sql > > Password: > > pg_restore: [archiver (db)] Error while PROCESSING TOC: > > pg_restore: [archiver (db)] Error from TOC entry 6; 2615 2200 SCHEMA public > postgres > > pg_restore: [archiver (db)] could not execute query: ERROR: must be owner > of schema public > > Command was: DROP SCHEMA public; > > pg_restore: [archiver (db)] could not execute query: ERROR: schema > "public" already exists > > Command was: CREATE SCHEMA public; > > pg_restore: [archiver (db)] Error from TOC entry 2663; 0 0 COMMENT SCHEMA > public postgres > > pg_restore: [archiver (db)] could not execute query: ERROR: must be owner > of schema public > > Command was: COMMENT ON SCHEMA public IS 'standard public schema'; > > pg_restore: WARNING: no privileges could be revoked for "public" > > pg_restore: WARNING: no privileges could be revoked for "public" > > pg_restore: WARNING: no privileges were granted for "public" > > pg_restore: WARNING: no privileges were granted for "public" > > WARNING: errors ignored on restore: 3 > > > > Wondering how can I suppress the Error and other messages seen above. > This is because you're restoring into the same database that you backed up from. I recommend creating a new database 'suresha_new' Then, restore into that new database. Once you've restored, you can: ALTER DATABASE suresha RENAME TO suresha_orig; ALTER DATABASE suresha_new RENAME TO suresha; --Scott > > > > > Thanks > > SureshA >
Re: [BUGS] BUG #5423: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initiate the connecti
On Thu, Apr 15, 2010 at 6:35 PM, Geoffrey Pitman wrote: Offlist reply posted back to list. How did you perform your install? (I think you're running Ubuntu 9.10). > > Did you use the repositories, or did you build it from source? > > If you used the Ubuntu repositories, have you checked the Community guide? > Located here: > > https://help.ubuntu.com/community/PostgreSQL > > The version data (in the guide) is not up-to-date, but you can always do an > aptitude search postgre at the CLI to find the appropriate version number. > > Also, it might not be on port 5432; I've seen some funky installs with > Ubuntu that put Postgre on 5433. You might want to check that? (though that > wouldn't be directly related to your reported issue) which is more likely a > permissions issue, or you're not launching the server as root--either via a > secondary script or maybe your init.rc script is wrong? > > > > On Thu, Apr 15, 2010 at 8:51 AM, Scott Mead > wrote: > >> >> On Wed, Apr 14, 2010 at 8:15 PM, Alex Soto Paez < >> alejandro.soto...@gmail.com> wrote: >> >>> >>> The following bug has been logged online: >>> >>> Bug reference: 5423 >>> Logged by: Alex Soto Paez >>> Email address: alejandro.soto...@gmail.com >>> PostgreSQL version: 8.4 >>> Operating system: linux 9.10 >>> Description:problems installing postgresql-8.4 deleted folder / >>> .s.PGSQL.lock not initiate the connecti >>> Details: >>> >>> problems installing postgresql-8.4 deleted folder / var / run / >>> postgresql / >>> .s.PGSQL.lock not initiate the connection to port 5432 >>> >>> when installing postgresql-8.4 is installed correctly while running the >>> command: >>> >>> $ Service postgresql-8.4 status >>> >>> Published online defautl port 5432, but at reboot the machine no longer >>> seems in line appears down and restart the server payable are parachute >>> with >>> the error: >>> >>> >>> $sudo /ect/init.d/postgresql-8.4 restart >>> >>> The PostgreSQL server failed to start. Please check the log output: >>> 2010-04-14 18:48:24 CDT FATAL: could not lock file >> postgresql >>> / .s.PGSQL.lock>>: no such file? directory >>> >>> >>> [Fail] >>> >>> run and hand it to guide the pid file and everything goes well but when >>> you >>> see another restart the computer I get the same error described above. >>> not >>> save the folder with the Pid and does not connect to port 5432 >>> >>> Someone can help me >>> >>> In advance thank you very much. >>> >>> >> Does the '/var/run/postgresql' directory exist and is it writeable by the >> postgres user? If it is not, I would say it's a bug for the packager of >> this install of postgres. Typically, postgres puts its lock / sockets in >> '/tmp'. You say linux, but don't say which linux, by your version string >> (9.10) I'm guessing that this is ubuntu? >> >> --Scott >> >> >> >> >>> -- >>> >>> 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] BUG #5424: Not able to Install
On 15/04/2010 10:14 PM, Aditya Vats wrote: The following bug has been logged online: Bug reference: 5424 Logged by: Aditya Vats Email address: aditya.v...@cerner.com PostgreSQL version: 8.4.2-1 Operating system: Windows Vista Description:Not able to Install Details: While installing I am getting an error saying : The password specified was incorrect.Please enter the correct password for the postgress windows user account. If you installed PostgreSQL before, you set a password then. You need to enter that password. If you only have 8.4 installed, ie you don't have any other PostgreSQL versions installed, then it's safe to reset the password for the postgres user account. It's also possible that due to a recently-discovered installer bug, if you mis-typed the password the first time it stored it anyway and *then* told you the passwords didn't match, in which case you'll probably have to reset the password. Unfortunately the PostgreSQL installer doesn't offer you any way to reset the password from within the installer. You can reset it using the standard windows tools. You should be able to find Computer Management in the Start menu, under All Programs -> Administrative Tools. If not, open up the Control Panel, switch it to classic view, open Administrative Tools, then Computer Management. Within Computer Management open up Local Users and Groups, then "Users". You'll see the postgres account there and can reset its password if required. -- Craig Ringer -- 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] Reset ACL to default for pg 8.0
Juan C. Aragon wrote:
> Thanks Bruce for replying.
>
> The ACL is display in the PgAdmin tool for Windows on the properties for a
> table or function. ACL is the Privileges. By default, when you create a new
> function or table, the ACL is null. However, if you add some privileges, and
> then remove all, the ACL is not longer null, it displays the brackets {}.
I can reproduce your reported behavior in psql, which I admit is odd:
test=> create table test(x int);
CREATE TABLE
test=> \pset null '(null)'
Null display is "(null)".
test=> grant all on test to postgres;
GRANT
test=> revoke all on test from postgres;
REVOKE
test=> select relacl from pg_class where relname = 'test';
relacl
{}
(1 row)
Community, do we want to make a permission reset cause the column to
become null?
> I just need to know if the brackets are normal when all the privileges are
> remove. Or how to reset the privileges (ACL) to default (null).
They are the same.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
--
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] BUG #5423: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initiate the connecti
On Thu, Apr 15, 2010 at 6:35 PM, Geoffrey Pitman wrote: Off-list reply posted to list How did you perform your install? (I think you're running Ubuntu 9.10). > > Did you use the repositories, or did you build it from source? > > If you used the Ubuntu repositories, have you checked the Community guide? > Located here: > > https://help.ubuntu.com/community/PostgreSQL > > The version data (in the guide) is not up-to-date, but you can always do an > aptitude search postgre at the CLI to find the appropriate version number. > > Also, it might not be on port 5432; I've seen some funky installs with > Ubuntu that put Postgre on 5433. You might want to check that? (though that > wouldn't be directly related to your reported issue) which is more likely a > permissions issue, or you're not launching the server as root--either via a > secondary script or maybe your init.rc script is wrong? > > > > On Thu, Apr 15, 2010 at 8:51 AM, Scott Mead > wrote: > >> >> On Wed, Apr 14, 2010 at 8:15 PM, Alex Soto Paez < >> alejandro.soto...@gmail.com> wrote: >> >>> >>> The following bug has been logged online: >>> >>> Bug reference: 5423 >>> Logged by: Alex Soto Paez >>> Email address: alejandro.soto...@gmail.com >>> PostgreSQL version: 8.4 >>> Operating system: linux 9.10 >>> Description:problems installing postgresql-8.4 deleted folder / >>> .s.PGSQL.lock not initiate the connecti >>> Details: >>> >>> problems installing postgresql-8.4 deleted folder / var / run / >>> postgresql / >>> .s.PGSQL.lock not initiate the connection to port 5432 >>> >>> when installing postgresql-8.4 is installed correctly while running the >>> command: >>> >>> $ Service postgresql-8.4 status >>> >>> Published online defautl port 5432, but at reboot the machine no longer >>> seems in line appears down and restart the server payable are parachute >>> with >>> the error: >>> >>> >>> $sudo /ect/init.d/postgresql-8.4 restart >>> >>> The PostgreSQL server failed to start. Please check the log output: >>> 2010-04-14 18:48:24 CDT FATAL: could not lock file >> postgresql >>> / .s.PGSQL.lock>>: no such file? directory >>> >>> >>> [Fail] >>> >>> run and hand it to guide the pid file and everything goes well but when >>> you >>> see another restart the computer I get the same error described above. >>> not >>> save the folder with the Pid and does not connect to port 5432 >>> >>> Someone can help me >>> >>> In advance thank you very much. >>> >>> >> Does the '/var/run/postgresql' directory exist and is it writeable by the >> postgres user? If it is not, I would say it's a bug for the packager of >> this install of postgres. Typically, postgres puts its lock / sockets in >> '/tmp'. You say linux, but don't say which linux, by your version string >> (9.10) I'm guessing that this is ubuntu? >> >> --Scott >> >> >> >> >>> -- >>> >>> 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] Reset ACL to default for pg 8.0
Bruce Momjian writes: > Community, do we want to make a permission reset cause the column to > become null? That's not a permission reset. >> I just need to know if the brackets are normal when all the privileges are >> remove. Or how to reset the privileges (ACL) to default (null). > They are the same. Nope, they're not. NULL implies the built-in-default permissions, which are quite different from the empty set. 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
