On 2 July 2013 09:30, Dean Rasheed wrote:
> I think the rewritten query should only use inheritance if inheritance
> was requested in the original query, *and* if inheritance was enabled
> in the view's query, per attached patch against HEAD.
On second thoughts, I think this should
_check"
>> DETAIL: Failing row contains (120, ABC, HELLO, 11000).
>> postgres=# select version();
>> version
>>
>>
>>
On 3 February 2013 09:16, Dean Rasheed wrote:
>> It looks like what the code is actually computing is the average X
>> position and average Y position of the points listed in the polygon.
Although, if that's really how it's being calculated, then that's not
really
t would balance if the edge was aligned at 45 degrees to the sides of
the L, cutting each edge in half. So the centroid is halfway along the
line that connects the midpoints of the L shape.
It's also easy to see that the centroid is definitely not at (0.5,
0.5) because the entire polygon
On 12 June 2012 21:27, Josh Kupershmidt wrote:
> On Sat, Jun 9, 2012 at 2:40 AM, Dean Rasheed wrote:
>
>> I noticed this while testing 9.2, but it seems to go back to at least
>> 8.3. Tab completion of function arguments doesn't work if the function
>> is schema-q
Thanks.
Out of curiosity why didn't the driver map the Postgresql UUID to a Java
UUID?
On 6/6/12 2:12 AM, "Kris Jurka" wrote:
>
>
>On Tue, 5 Jun 2012, Dean Schulze wrote:
>
>>
>> I'm using Hibernate (3.6 and 4.0) with Postgresql 9.1. Our tab
covers all the edge cases.
Regards,
Dean
tab-complete.patch
Description: Binary data
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
I'm using Hibernate (3.6 and 4.0) with Postgresql 9.1. Our tables have UUIDs
in them and your driver is trying to convert UUIDs to longs:
Caused by: org.postgresql.util.PSQLException: Bad value for type long :
dbada1e4-a165-4601-b34e-d08428cd81df
at
org.postgresql.jdbc2.AbstractJdbc2ResultS
The following bug has been logged on the website:
Bug reference: 6380
Logged by: Dean Schulze
Email address: dean.w.schu...@gmail.com
PostgreSQL version: 9.1.2
Operating system: CENTOS 6
Description:
I've tried both the .rpm from openscg and the .linux.run inst
d'));
ERROR: function pgp_sym_encrypt(unknown, unknown) does not exist
It works fine for me here. Is pgp_sym_encrypt listed in this output?
\dx+ pgcrypto
My guess is that the OP has installed the extension in one database
(maybe "postgres") and tries to use it in anoth
The following bug has been logged on the website:
Bug reference: 6363
Logged by: Dean Schulze
Email address: dean.w.schu...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Windows 7 Pro 64-bit
Description:
The following worked in 8.4, but fails in 9.1
The following bug has been logged online:
Bug reference: 6224
Logged by: Dean Heller
Email address: dhel...@tainstruments.com
PostgreSQL version: 4.95.170.0
Operating system: Windows 7 64bit
Description:Installation Error of dotconnect for postgre SQL
Professional
e in _bt_preprocess_keys(), which discards the
"a > 1" predicate in favour of the "a is null" predicate on the
grounds that "null > 1" in a nulls-last index.
It looks like a previous revision had the right check, based on the
logic that x IS NULL is inco
Failed.
The problem is that the test for overflow of the arg position doesn't
catch all cases. The simplest solution is to just tweak the comparison
at varlena.c:3840 (patch attached) although maybe there are neater
ways...
Regards,
Dean
diff --git a/src/backend/utils/adt/varlena.c b/src/ba
that, due to limited precision of
the output format.
Using the arcsin(..) form of the Haversine formula cures that -
http://en.wikipedia.org/wiki/Great-circle_distance
Regards,
Dean
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
es, perhaps you could try adding the following to your Hibernate
configuration:
true 1, false 0
Regards,
Dean
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Sorry, I meant to cc this to -bugs as well as -hackers
-- Forwarded message --
From: Dean Rasheed
Date: 18 August 2010 18:29
Subject: Per-tuple memory leak in 9.0
To: pgsql-hack...@postgresql.org
While testing triggers, I came across the following memory leak.
Here's a s
t is
specified as DEFERRABLE it will be checked at the end of the statement
rather than as each row is updated. The constraint check may also be
DEFERRED until the end of the current transaction allowing updates to
be spread over multiple SQL commands.
"""
Regards,
Dean
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 9 June 2010 20:56, Robert Haas wrote:
> On Wed, Jun 9, 2010 at 3:50 PM, Tom Lane wrote:
>> Dean Rasheed writes:
>>> Hmm. Well it's quite subjective, but IMO it's already more readable
>>> than JSON regardless of whether or not values are quoted, simpl
On 9 June 2010 19:50, Robert Haas wrote:
> After thinking about this further, I think I'd still like to take one
> more crack at fixing this without quoting absolutely everything. I
> argued against this feature, but we decided to take it, and it seems
> that one of the major arguments that is be
On 9 June 2010 14:14, Robert Haas wrote:
> On Wed, Jun 9, 2010 at 8:46 AM, Dean Rasheed wrote:
>> On 9 June 2010 03:48, Robert Haas wrote:
>>> please test.
>>
>> Well your patch definitely fixes my original bug, and AFAICT always
>> produces valid YAML output
pace, for example.
>
> It seemed to me, in particular, that someone might use a # symbol,
> like "# of Iterations".
>
Then the resulting XML tagname would be invalid too
I think they would soon realise/be told that it was a bad idea.
Dean
--
Sent via pgsql-bugs mailing l
this
>> by accident.
>
> Really? What likely key names would be in need of quoting? I can't
> imagine accepting a field name that contains punctuation or leading
> or trailing whitespace, for example.
>
And any of those things would break the XML output too.
I can'
On 9 June 2010 16:05, Robert Haas wrote:
> On Wed, Jun 9, 2010 at 11:03 AM, Tom Lane wrote:
>> Robert Haas writes:
>>> On Wed, Jun 9, 2010 at 9:35 AM, Dean Rasheed
>>> wrote:
>>>>> Does anyone care that Alias will sometimes be a string, and somet
ing too.
But this is also a pretty obscure case that probably only someone
deliberately trying to be awkward would do (which is me, with my
tester hat on :-)).
Regards,
Dean
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 9 June 2010 12:32, Robert Haas wrote:
> On Wed, Jun 9, 2010 at 7:23 AM, Dean Rasheed wrote:
>> On 9 June 2010 12:07, Robert Haas wrote:
>>> On Wed, Jun 9, 2010 at 2:58 AM, Dean Rasheed
>>> wrote:
>>>> On 9 June 2010 03:48, Robert Haas wrote:
>
On 9 June 2010 12:07, Robert Haas wrote:
> On Wed, Jun 9, 2010 at 2:58 AM, Dean Rasheed wrote:
>> On 9 June 2010 03:48, Robert Haas wrote:
>>> Er, I should also say, thanks for the report, and please test. I am
>>> definitely not an expert on YAML.
>>>
&g
On 9 June 2010 07:58, Dean Rasheed wrote:
> I prefer my patch - but then I suppose I would say that :-)
>
Seriously though, I can think of a number of good arguments in favour
of the "quote all string values unconditionally" approach:
- It's the simplest, least obtrusive fi
hat's been said on this thread, I still
prefer my patch - but then I suppose I would say that :-)
Cheers,
Dean
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
not just everything containing a special character,
it's also anything with leading or trailing whitespace, and empty
strings (not sure that can ever happen in practice).
It's because of the potential for bugs in this area, that I'd propose
just quoting everything (except numeric values) a
ing values, and only have numeric
values unquoted. This is not really any less human readable, and is
far more machine readable.
Patch attached.
- Dean
*** ./src/backend/commands/explain.c.orig 2010-06-07 08:49:06.0 +0100
--- ./src/backend/commands/explain.c 2010-06-07 09:09:44.00
The following bug has been logged online:
Bug reference: 5343
Logged by: Rob Dean
Email address: rob.d...@pressassociation.com
PostgreSQL version: 8.3
Operating system: linux
Description:Documentation error for pg_dump
Details:
The last sentence of the penultimate
The following bug has been logged online:
Bug reference: 5005
Logged by: Dean Schulze
Email address: dean.w.schu...@comcast.net
PostgreSQL version: 8.3.7
Operating system: Win XP
Description:unique constraint considers nulls to be equal
Details:
When I apply this
ble hint would help, as
well as re-wording the error message:
ERROR: deferrable constraint "foo" does not exist
HINT: You must specify the name of a constraint declared with the
DEFERRABLE option.
- Dean
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chang
test set i = i + 1;
> UPDATE 3
>
> shouldn't it raise exception? and work *only* if i set the constraint to
> deferred?
>
"Immediate" actually means at the end of the statement rather than
after each row for deferrable constraints. See
http://developer.postgr
The following bug has been logged online:
Bug reference: 4434
Logged by: Dean Rasheed
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: SuSE 10.3 64-bit
Description:Error inserting into view - unrecognized node type: 313
Details:
I&#
The following bug has been logged online:
Bug reference: 3718
Logged by: Dean
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Linux (opensuse 10.3 64-bit) and Windows 2000 SP4
Description:Unexpected undefined_table error after creating
The following bug has been logged online:
Bug reference: 1645
Logged by: Seamus Dean
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.2
Operating system: Red Hat Linux 7.3
Description:Auto complete SQL "COPY" have problems.
Details:
When I using t
38 matches
Mail list logo
