[BUGS] RPMS don't work for 2.2.17
Alex Finck ([EMAIL PROTECTED]) reports a bug with a severity of 4 The lower the number the more severe it is. Short Description RPMS don't work for 2.2.17 Long Description I get this message: IpcMemoryCreate: memKey=155356396 , size=760632 , permission=384IpcMemoryCreate: shmget(..., create, ...) failed: Invalid argument even if I have compiled the IPC support in the running kernel which is 2.2.17. This is for the 7.0.2-6mdk I think this is because the RPMS are based on a different kernel. I send you this bug repport because it seems that Mandrake which distributes the RPMS has simply changed the name of the RPMS without recompiling. Alex. Sample Code No file was uploaded with this report
Re: [BUGS] Joins on over 10 tables returns unreliable results
[EMAIL PROTECTED] writes: > Running Postgres version 7.01 on Redhat linux 6.2. When joining on > more than 10 tables not all of the expected results are returned. > The query can be repeated several times, with different result sets > when the data itself is static. The most common result is the return > of only one record. 11 tables seems to be the magic limit. Joins on > 10 tables works without a hitch. This join was based on a column id > that exists in all of the tables. This seems to be a problem in the genetic query optimizer. But to examine closer we'd really need to get sample data and queries to reproduce this. For now you can SET geqo TO 'off'; to disable this. -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Re: [BUGS] RPMS don't work for 2.2.17
[EMAIL PROTECTED] writes: > IpcMemoryCreate: memKey=155356396 , size=760632 , > permission=384IpcMemoryCreate: shmget(..., create, ...) > failed: Invalid argument This means that you don't have enough shared memory. See FAQ. -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Re: [BUGS] RPMS don't work for 2.2.17
[EMAIL PROTECTED] wrote: > > Alex Finck ([EMAIL PROTECTED]) reports a bug with a severity of 4 > The lower the number the more severe it is. > > Short Description > RPMS don't work for 2.2.17 > > Long Description > I get this message: > > IpcMemoryCreate: memKey=155356396 , size=760632 , > permission=384IpcMemoryCreate: shmget(..., create, ...) > failed: Invalid argument > > even if I have compiled the IPC support in the running kernel which is 2.2.17. > > This is for the 7.0.2-6mdk I think this is because the RPMS are based on a different >kernel. I send you this bug repport because it seems that Mandrake which distributes >the RPMS has simply changed the name of the RPMS without recompiling. Which distribution are you running? There is a newer RPM available on the postgresql ftp site (which I am about to announce, once I get everything moved into place) -- ftp.postgresql.org/pub/binary/v7.0.2/RedHat-6.x/RPMS/postgresql*7.0.2-21.i386.rpm If you want to recompile the RPM from source, here's what you do: Download the source RPM: ftp.postgresql.org/pub/binary/v7.0.2/RedHat-6.x/SRPMS/postgresql-7.0.2-21.src.rpm Install the source RPM: rpm -i postgresql-7.0.2-21.src.rpm Make sure you have a full build environment: You need C and C++ installed and working, you need tcl/tk 8 installed and working, you need python and python-devel installed and working, you need the X11 development headers and libraries installed and working (XFree86-devel on most distributions) -- on RedHat 7 you need rpm-build installed as well. Now, once you know everything you need is installed, cd to the RPM build area on your box (for RedHat, this is /usr/src/redhat, for TurboLinux this is /usr/src/turbo, for Mandrake this is /usr/src/RPM (I think), for SuSE this is /usr/src/packages (but, for SuSE you need to use _THEIR_ RPMset for 7.0.2, which is part of SuSE 7.0), and for Caldera this is /usr/src/OpenLinux (but the build won't work due to Caldera using a positively archaic version of RPM -- 2.5.5). The build will work just fine for Mandrake, TurboLinux, and RedHat's 6.2 and 7.0 -- the build will fail for RedHat 6.1, but the binaries for 6.2 should install on 6.1. And, as Peter said, make sure you have enough shared memory before you invest alot of time in rebuilding RPM's. Also, Mandrake typically builds for Pentium and higher -- you may have a CPU compatibility issue. Mandrake recompiles all their stuff -- but it is typically compiled at a higher optimization level than RedHat's stuff, as well as being compiled with a different compiler (at least in the past), and against different glibc's (some of the time). -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
[BUGS]
Carol GUINEBERTChef de projets CIPE - MEDIAPLACECentre Informatique Presse Edition41, rue Greneta75002 PARIS - FRANCEE-mail : [EMAIL PROTECTED]Tél : 01.53.00.73.12Fax : 01.53.00.10.02
[BUGS] webmaster@postgres.org gives user unknown
- Forwarded message from Mail Delivery Subsystem <[EMAIL PROTECTED]> - Date: Tue, 31 Oct 2000 12:50:35 -0500 (EST) From: Mail Delivery Subsystem <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Returned mail: see transcript for details Auto-Submitted: auto-generated (failure) The original message was received at Tue, 31 Oct 2000 12:50:34 -0500 (EST) from www.tummy.com [216.17.150.34] - The following addresses had permanent fatal errors - <[EMAIL PROTECTED]> (reason: 550 5.1.1 User unknown) - Transcript of session follows - ... while talking to localhost: >>> RCPT To: <<< 550 5.1.1 User unknown 550 5.1.1 <[EMAIL PROTECTED]>... User unknown Reporting-MTA: dns; mail.postgresql.org Received-From-MTA: DNS; www.tummy.com Arrival-Date: Tue, 31 Oct 2000 12:50:34 -0500 (EST) Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.1.1 Diagnostic-Code: X-Unix; 550 5.1.1 User unknown Last-Attempt-Date: Tue, 31 Oct 2000 12:50:35 -0500 (EST) -- http://www.tummy.com/ Consulting and Software for Linux and Unix KRUD - Kevin's Red Hat Uber Distribution - the Freshest Red Hat every month
[BUGS] new index page for documentation
I found the existing index page hard to navigate, so I made a new version.
Evelyn Mitchell
[EMAIL PROTECTED]
PostgreSQL
= 4)
{
img('s1');
img('s2');
img('s7');
img('s8');
img('s9');
img('s10');
}
//->
Documentation
Current Release Docs (ver 7.0)
Current Development Docs
Version 6.5
admin Online Postscript HTML
postgres Online HTML
programmer Online Postscript HTML
tutorial Online Postscript HTML
user Online Postscript HTML
Version 7.0
admin Online Postscript
HTML Postscript A4
man HTML
postgres Online HTML
programmer Online HTML Postscript
Postscript A4
tutorial Online HTML Postscript Postscript A4
user Online HTML Postscript Postscript A4
--
http://www.tummy.com/ Consulting and Software for Linux and Unix
KRUD - Kevin's Red Hat Uber Distribution - the Freshest Red Hat every month
[BUGS] bug
Your name : Dave Orr Your email address : [EMAIL PROTECTED] System Configuration - Architecture (example: Intel Pentium) :Intel Pentium Operating System (example: Linux 2.0.26 ELF) :Linux 2-2.14-lmdklinus PostgreSQL version (example: PostgreSQL-7.0): PostgreSQL-7.0.2 Compiler used (example: gcc 2.8.0) :gcc 2.95.2 Please enter a FULL description of your problem: I create two tables where a field in one is constrained to only contain values that exist in a field in the other. I create a group and grant all on the constrained table to that group. I grant the group select on the constraining table. I add a user to the group. When the user tries to insert into the constrained table, I get permission denied. I need to grant update on the constraining table in order to insert a record into the constrained table Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: -- Create a database named test. Run this script into it: create table by_me( needed int primary key ); insert into by_me values(1); create table im_constrained( field1 int, constraint im_constrained_by_me foreign key ( field1) references by_me match full on delete no action ); create group test; grant select,update,delete,insert on im_constrained to group test; grant select on by_me to group test; Add a user to group "test" suid to that user and try to add a record test=> insert into im_constrained values(1); ERROR: by_me: Permission denied. If you know how this problem might be fixed, list the solution below: -
Re: [BUGS] 68E5-58AF-9EBF : CONFIRM from pgsql-bugs (set)
reject
Re: [BUGS] bug
This is a known problem in 7.0.x. The insert/update constrained table case should be fixed in 7.1. You can get details about it in the mailing list archives. Stephan Szabo [EMAIL PROTECTED] On Tue, 31 Oct 2000, David Orr wrote: > Your name : Dave Orr > Your email address: [EMAIL PROTECTED] > > > System Configuration > - > Architecture (example: Intel Pentium) :Intel Pentium > > Operating System (example: Linux 2.0.26 ELF):Linux 2-2.14-lmdklinus > > PostgreSQL version (example: PostgreSQL-7.0): PostgreSQL-7.0.2 > > Compiler used (example: gcc 2.8.0) :gcc 2.95.2 > > > Please enter a FULL description of your problem: > > > I create two tables where a field in one is constrained to only contain values > that exist in a field in the other. I create a group and grant all on the > constrained table to that group. I grant the group select on the constraining > table. I add a user to the group. When the user tries to insert into the > constrained table, I get permission denied. > > I need to grant update on the constraining table in order to insert a record > into the constrained table > > > Please describe a way to repeat the problem. Please try to provide a > concise reproducible example, if at all possible: > -- > Create a database named test. Run this script into it: > > create table by_me( > needed int primary key > ); > insert into by_me values(1); > > create table im_constrained( > field1 int, > > constraint im_constrained_by_me foreign key ( field1) > references by_me > match full > on delete no action > ); > > create group test; > grant select,update,delete,insert on im_constrained to group test; > grant select on by_me to group test; > > Add a user to group "test" > suid to that user and try to add a record > > test=> insert into im_constrained values(1); > ERROR: by_me: Permission denied. > > If you know how this problem might be fixed, list the solution below: > - >
Re: [BUGS] webmaster@postgres.org gives user unknown
fixed, thanks ...
On Tue, 31 Oct 2000, Evelyn Mitchell wrote:
> - Forwarded message from Mail Delivery Subsystem
><[EMAIL PROTECTED]> -
>
> Date: Tue, 31 Oct 2000 12:50:35 -0500 (EST)
> From: Mail Delivery Subsystem <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: Returned mail: see transcript for details
> Auto-Submitted: auto-generated (failure)
>
> The original message was received at Tue, 31 Oct 2000 12:50:34 -0500 (EST)
> from www.tummy.com [216.17.150.34]
>
>- The following addresses had permanent fatal errors -
> <[EMAIL PROTECTED]>
> (reason: 550 5.1.1 User unknown)
>
>- Transcript of session follows -
> ... while talking to localhost:
> >>> RCPT To:
> <<< 550 5.1.1 User unknown
> 550 5.1.1 <[EMAIL PROTECTED]>... User unknown
>
> Reporting-MTA: dns; mail.postgresql.org
> Received-From-MTA: DNS; www.tummy.com
> Arrival-Date: Tue, 31 Oct 2000 12:50:34 -0500 (EST)
>
> Final-Recipient: RFC822; [EMAIL PROTECTED]
> Action: failed
> Status: 5.1.1
> Diagnostic-Code: X-Unix; 550 5.1.1 User unknown
> Last-Attempt-Date: Tue, 31 Oct 2000 12:50:35 -0500 (EST)
>
>
> --
> http://www.tummy.com/ Consulting and Software for Linux and Unix
> KRUD - Kevin's Red Hat Uber Distribution - the Freshest Red Hat every month
>
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
