The following bug has been logged on the website:
Bug reference: 6643
Logged by: Tomonari Katsumata
Email address: katsumata.tomon...@po.ntts.co.jp
PostgreSQL version: Unsupported/Unknown
Operating system: RHEL 6.2 x86_64
Description:
Hi,
Now, I'm testing PostgreSQL
On 16.05.2012 13:39, katsumata.tomon...@po.ntts.co.jp wrote:
Now, I'm testing PostgreSQL 9.2 Beta 1.
And I have a problem.
Steps to procedure are bellow.
1. CREATE DATABASE
export LANG=C
initdb -D $PGDATA -E SQL_ASCII
pg_ctl start
createdb testdb
2. CREATE TABLE
psql -d testdb -
On 16.05.2012 13:47, Heikki Linnakangas wrote:
This sounds like a bug in the new page-at-a-time behavior in COPY. Can
you send me a self-contained test, including the test data?
Never mind. After staring at the code for a while, I spotted the bug,
and was able to reproduce with a simpler case.
Hi, Heikki
I'm sorry, forgotten attach files.
I've tryed to send mail with files,
but I could not...
(I think this is my mail server problem.)
Thank you very much for fixing it!
(2012/05/16 20:14), Heikki Linnakangas wrote:
On 16.05.2012 13:47, Heikki Linnakangas wrote:
This sounds like a b
Martin Pitt writes:
> while packaging 9.2 beta 1 for Debian/Ubuntu the postgresql-common
> test suite noticed a regression: It seems that pg_restore --data-only
> now skips the current value of sequences, so that in the upgraded
> database the sequence counter is back to the default.
I believe th
The following bug has been logged on the website:
Bug reference: 6641
Logged by: Chris Ruprecht
Email address: ch...@cdrbill.com
PostgreSQL version: 9.1.3
Operating system: Mac OS X 10.7.4
Description:
running configure as such:
export MACOSX_DEPLOYMENT_TARGET=10.7
e
On Wed, May 16, 2012 at 9:08 AM, Tom Lane wrote:
> Martin Pitt writes:
> > while packaging 9.2 beta 1 for Debian/Ubuntu the postgresql-common
> > test suite noticed a regression: It seems that pg_restore --data-only
> > now skips the current value of sequences, so that in the upgraded
> > databa
The following bug has been logged on the website:
Bug reference: 6645
Logged by: Evna Carroll
Email address: m...@evancarroll.com
PostgreSQL version: 9.1.2
Operating system: Linux
Description:
This is a cross post from dba.stackexchange.com:
http://dba.stackexchange.c
On Wed, May 16, 2012 at 10:47 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6645
> Logged by: Evna Carroll
> Email address: m...@evancarroll.com
> PostgreSQL version: 9.1.2
> Operating system: Linux
> Description:
>
> This is a cross post f
Alex Hunsaker writes:
> That being said it seems we failed to take any magic (aka string
> overloads) that a blessed reference might have. Ill see about
> submitting a patch for 9.3 (9.2 just entered beta). Anyone have any
> thoughts on if we should backpatch a fix?
Right offhand I'd be +1 for ma
On Wed, May 16, 2012 at 11:53 AM, Tom Lane wrote:
> Alex Hunsaker writes:
>> That being said it seems we failed to take any magic (aka string
>> overloads) that a blessed reference might have. Ill see about
>> submitting a patch for 9.3 (9.2 just entered beta). Anyone have any
>> thoughts on if w
Excerpts from tulio.carrasco's message of mar may 15 21:45:00 -0400 2012:
> In Spanish every vowel has the same precedence value even with or without
> any type of accent, so: a = á = ä = A = Á = Ä
> In which due dad column has the same value it uses the mum column and if
> they also have the sa
The following bug has been logged on the website:
Bug reference: 6644
Logged by: Karl Walbrecht
Email address: kwalbre...@cghtech.com
PostgreSQL version: 9.0.3
Operating system: SunOS 5.10
Description:
geom.ArcToStreight(integer) is a function which returns the follow
The following bug has been logged on the website:
Bug reference: 6646
Logged by: Steven Huwig
Email address: st...@empiricalthought.com
PostgreSQL version: 9.1.3
Operating system: Linux
Description:
I am trying to raise standard SQL errors from inside PL/Python code.
kwalbre...@cghtech.com writes:
> geom.ArcToStreight(integer) is a function which returns the following type:
> The following queries show 1) the total number of rows. 2) the number of
> null rows. 3) the number of not null rows.
> The problem is that results of query 2 + the results of query 3 shou
Thank you very much Álvaro,
As far as I understood from someone who knows about ;) "...the SQL
standard indicates to order according the first column and consider the
second column only for those records which first column has identical order
values..."
The bug I refer to is that first column is
16 matches
Mail list logo
