On Fri, Oct 30, 2009 at 08:51:57PM -0700, John R Pierce wrote:
> Tom Lane wrote:
>> There is special-purpose software out there that can compute
>> exactly with rational numbers, but you aren't likely to find it
>> embedded in any general-purpose tools like databases --- the
>> use-case just isn't
Hello
2009/10/31 Jeff Shanab :
>
> The following bug has been logged online:
>
> Bug reference: 5154
> Logged by: Jeff Shanab
> Email address: jsha...@earthlink.net
> PostgreSQL version: 8.3.5
> Operating system: Linux
> Description: ERROR: cannot assign non-composite
Tom Lane wrote:
There is special-purpose software out there that can compute exactly
with rational numbers, but you aren't likely to find it embedded in any
general-purpose tools like databases --- the use-case just isn't wide
enough. One reason why not is that it'll still fall down on irrationa
"Pierre" writes:
> postmaster/postmaster.o: In function `ClosePostmasterPorts':
> postmaster.c:(.text+0xadb): undefined reference to `DNSServiceRefSockFD'
> postmaster/postmaster.o: In function `StartChildProcess':
> postmaster.c:(.text+0x1d9f): undefined reference to `DNSServiceRefSockFD'
> postm
Robert Haas writes:
> In general, floating point arithmetic is inaccurate and sucky. That
> has nothing to do with PostgreSQL; it's just life.
Actually, I think these examples are being done in "numeric" not float8.
Your comment stands though --- 1.0/3.0 does not give the exact rational
number 1
The following bug has been logged online:
Bug reference: 5155
Logged by: Pierre
Email address: pierre...@9online.fr
PostgreSQL version: 8.5a2
Operating system: GNU/Linux
Description:Error compiling postgresql-8.5alpha2
Details:
[...]
make -C ../../src/timezone all
m
On Fri, Oct 30, 2009 at 1:39 AM, Gray wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5150
> Logged by: Gray
> Email address: g...@ms-irk.ru
> PostgreSQL version: 8.2.6
> Operating system: i686-pc-linux-gnu
> Description: math bug
> Details:
>
>
On Thu, Oct 29, 2009 at 6:14 PM, Don Fox wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5149
> Logged by: Don Fox
> Email address: donf...@mac.com
> PostgreSQL version: 8.4.1
> Operating system: Mac X Snowleopard
> Description: Can't untar the s
The following bug has been logged online:
Bug reference: 5154
Logged by: Jeff Shanab
Email address: jsha...@earthlink.net
PostgreSQL version: 8.3.5
Operating system: Linux
Description:ERROR: cannot assign non-composite value to a row
variable
Details:
As discussed
On Fri, 2009-10-30 at 17:35 -0400, Tom Lane wrote:
> I think he has a build of 8.1.x for RHEL-4, though I could be wrong).
Yes, we have:
http://yum.pgsqlrpms.org/8.1/redhat/rhel-4-x86_64/repoview/
http://yum.pgsqlrpms.org/8.1/redhat/rhel-4-i386/repoview/
Boris, repo howto is here:
http://yum.pgs
"Boris Folgmann" writes:
> Currently I'm using postgresql-8.1.15-1.el4s1.1 from the centosplus
> repository for CentOS 4.8. All updates applied, kernel is
> 2.6.9-89.0.11.ELsmp.
> I know that 8.1.18 is out, but haven't found something in the release-notes
> about problems with max_fsm_pages. Anywa
"Pierre" writes:
> checking for SSL_library_init in -lssl... no
> configure: error: library 'ssl' is required for OpenSSL
> I just installed the last openssl release in its default location.
If you are using a distribution that provides separate -devel
subpackages, you probably need to install o
Boris Folgmann wrote:
> Currently I'm using postgresql-8.1.15-1.el4s1.1 from the centosplus
> repository for CentOS 4.8. All updates applied, kernel is
> 2.6.9-89.0.11.ELsmp.
> I know that 8.1.18 is out, but haven't found something in the release-notes
> about problems with max_fsm_pages. Anyway, t
Stefan Kaltenbrunner writes:
> However the error seems to go away after an ANALYZE... so I wonder if
> this is just another case of "if we missestimated the size of the
> hashtable we are doomed"
Actually, what seems to be happening on a 32-bit machine is that
ExecChooseHashTableSize sets nbatc
Stefan Kaltenbrunner writes:
> ok just assembled a new testcase from the querylog of the tool:
> http://www.kaltenbrunner.cc/files/rand_gen_crash.sql
Ah, that works (or should I say fails). Will take a look.
> However the error seems to go away after an ANALYZE... so I wonder if
> this is just
Greg Stark wrote:
On Fri, Oct 30, 2009 at 11:22 AM, Stefan Kaltenbrunner
wrote:
ok I now see why you (and I) failed to reproduce the problem - it only
causes clusters/databases to crash that were actually generated using the
upthread mentioned script. it does NOT fail using a dump generated by
On Fri, Oct 30, 2009 at 11:22 AM, Stefan Kaltenbrunner
wrote:
> ok I now see why you (and I) failed to reproduce the problem - it only
> causes clusters/databases to crash that were actually generated using the
> upthread mentioned script. it does NOT fail using a dump generated by a
> database th
Stefan Kaltenbrunner wrote:
Tom Lane wrote:
Stefan Kaltenbrunner writes:
this is 8.5a2 configured with ./configure --enable-cassert
--enable-debug and just default settings(ie plain initdb with
default settings).
The OS is Debian Lenny/AMD64.
Huh. That should not be noticeably different
S. Neumann wrote:
> When exporting databases using pg_dump column types that are 'bigserial'
> become 'bigint'. This problem did not occur on 8.0.8 on linux.
Yeah, but this is not a bug. There are later commands that attach a
sequence to the default value of the column, effectively turning it in
Tom Lane wrote:
Stefan Kaltenbrunner writes:
this is 8.5a2 configured with ./configure --enable-cassert
--enable-debug and just default settings(ie plain initdb with default
settings).
The OS is Debian Lenny/AMD64.
Huh. That should not be noticeably different from my F11/Xeon64
machine ..
The following bug has been logged online:
Bug reference: 5153
Logged by: Pierre
Email address: pierre...@9online.fr
PostgreSQL version: 8.5a2
Operating system: GNU/Linux
Description:Problem configuring postgresql-8.5alpha2 with SSL
Details:
[...]
checking for inflat
The following bug has been logged online:
Bug reference: 5152
Logged by: S. Neumann
Email address: simon.neum...@communology.com
PostgreSQL version: 8.3.7 and 8.4.1
Operating system: Microsoft Windows
Description:Exporting databases with pg_dump changes 'bigserial' to
The following bug has been logged online:
Bug reference: 5151
Logged by: Boris Folgmann
Email address: bo...@folgmann.de
PostgreSQL version: 8.1.15
Operating system: CentOS release 4.8 (Final)
Description:autovacuum process segfaults when max_fsm_pages are too
low
Det
The following bug has been logged online:
Bug reference: 5150
Logged by: Gray
Email address: g...@ms-irk.ru
PostgreSQL version: 8.2.6
Operating system: i686-pc-linux-gnu
Description:math bug
Details:
select 1/3*3,(1.0/3.0)*3.0,floor((1.0/3.0)*3.0);
returns
0, 1, 0
Hi Tom,
Thanks for you reply, but i don't quite get it.
"The view is owned by user1 and what the view can access is determined by
user1's permissions"
Why? I don't get it.
On one hand, if user1 can not access tb2, he should not be able to create the
view based on tb2.
On the other hand, user
The following bug has been logged online:
Bug reference: 5149
Logged by: Don Fox
Email address: donf...@mac.com
PostgreSQL version: 8.4.1
Operating system: Mac X Snowleopard
Description:Can't untar the src code file
Details:
tar -x post*.tar
^C
c-76-123-226-197:Down
Stefan Kaltenbrunner writes:
> this is 8.5a2 configured with ./configure --enable-cassert
> --enable-debug and just default settings(ie plain initdb with default
> settings).
> The OS is Debian Lenny/AMD64.
Huh. That should not be noticeably different from my F11/Xeon64
machine ... but I stil
Jonathan Hayward wrote:
The following bug has been logged online:
Bug reference: 5148
Logged by: Jonathan Hayward
Email address: jonathan.hayw...@pobox.com
PostgreSQL version: 8.1.x
Operating system: Gentoo
Description:Email to pgsql-bugs@postgresql.org bounces:
Deta
The following bug has been logged online:
Bug reference: 5148
Logged by: Jonathan Hayward
Email address: jonathan.hayw...@pobox.com
PostgreSQL version: 8.1.x
Operating system: Gentoo
Description:Email to pgsql-bugs@postgresql.org bounces:
Details:
I sent the followi
Tom Lane wrote:
Stefan Kaltenbrunner writes:
uploaded a dump of the dataset here:
http://www.kaltenbrunner.cc/files/rand_gen_data.sql
and the query that causes the segfault:
http://www.kaltenbrunner.cc/files/rand_gen_query.sql
[ scratches head... ] Still no crash here, and I tried it on a co
Stefan Kaltenbrunner writes:
> uploaded a dump of the dataset here:
> http://www.kaltenbrunner.cc/files/rand_gen_data.sql
> and the query that causes the segfault:
> http://www.kaltenbrunner.cc/files/rand_gen_query.sql
[ scratches head... ] Still no crash here, and I tried it on a couple
differe
"hx.li" writes:
>> This is not a bug. The view is owned by user1 and what the view can
>> access is determined by user1's permissions, independently of who is
>> calling it.
> So I think it should not have a permission error when run "select * from
> view1".
No, that would be a bad idea. Your
32 matches
Mail list logo
