Seems that the contrib regression tests, namely the cash and oid tests of
the btree_gist contrib module, are failing after the recent commit to
widen the money type to 64 bits. Example:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=mongoosedt=2007-01-03%2005:30:01
Also, on a slightly
On Tue, 2 Jan 2007, Jeremy Drake wrote:
Seems that the contrib regression tests, namely the cash and oid tests of
the btree_gist contrib module, are failing after the recent commit to
widen the money type to 64 bits. Example:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=mongoosedt=2007
It looks like pltcl regression tests are failing due to the recent ORDER
BY ... USING change.
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=mongoosedt=2007-01-09%2002:30:01
--
Horse sense is the thing a horse has which keeps it from betting on
people.
-- W. C. Fields
On Tue, 23 Jan 2007, Magnus Hagander wrote:
On Tue, Jan 23, 2007 at 09:31:40AM -0500, Andrew Dunstan wrote:
Magnus Hagander wrote:
Hi!
I get failures for the largeobject regression tests on my vc++ build. I
don't think this has ever worked, given that those tests are fairly new.
Any
On Wed, 24 Jan 2007, Peter Eisentraut wrote:
Teodor Sigaev wrote:
If there aren't objections then we plan commit patch tomorrow or
after tomorrow.
I still haven't heard any argument for why this would be necessary or
desirable at all, other than that it looks better for marketing
On Wed, 24 Jan 2007, Martijn van Oosterhout wrote:
On Wed, Jan 24, 2007 at 09:38:06PM +0100, Stefan Kaltenbrunner wrote:
sure that ISP is a bit stupid(especially wrt plpgsql) - but tsearch2 in
the current version is actually imposing some additional(often
non-trivial) complexity for things
On Wed, 24 Jan 2007, Tom Lane wrote:
[ redirecting thread from -patches to -hackers for wider comment ]
Jeremy Drake [EMAIL PROTECTED] writes:
On Wed, 24 Jan 2007, Tom Lane wrote:
Note I'm not arguing against allowing it to be on by default, I just
want to be sure there is a way
On Wed, 24 Jan 2007, Jeremy Drake wrote:
I am digging through the code looking at this, and I have a question. As
far as I can tell, there is currently no owner for a pg_language entry.
Is this correct or is ownership information stored somewhere other than
the pg_language relation? Are you
On Wed, 24 Jan 2007, Tom Lane wrote:
* For an untrusted language: must be superuser to either create or use
the language (no change from current rules). Ownership of the
pg_language entry is really irrelevant, as is its ACL.
* For a trusted language:
* if pg_pltemplate.something is ON:
I am wanting to write some new C functions which leverage postgresql's
existing regexp code in an extension module. I notice that the functions
RE_compile_and_cache and RE_compile_and_execute in
src/backend/util/regexp.c contain the code necessary to connect the regexp
code in src/backend/regex
On Thu, 1 Feb 2007, Tom Lane wrote:
Jeremy Drake [EMAIL PROTECTED] writes:
Is there some specific reason that these functions are static,
Yeah: not cluttering the global namespace.
Is there a reason for not putting your new code itself into regexp.c?
Not really, I just figured it would
On Thu, 1 Feb 2007, David Fetter wrote:
On Thu, Feb 01, 2007 at 05:11:30PM -0800, Jeremy Drake wrote:
Anyway, the particular thing I was writing was a function like
substring(str FROM pattern) which instead of returning just the
first match group, would return an array of text containing
On Thu, 1 Feb 2007, David Fetter wrote:
Yes, although it might have the same name, as in regex_match(pattern
TEXT, string TEXT, return_pre_and_post BOOL).
The data structure could be something like
TYPE matches (
prematch TEXT,
matchTEXT[],
postmatch TEXT
)
I just
On Fri, 2 Feb 2007, Jeremy Drake wrote:
jeremyd=# select * from regexp_matches('foobarbequebaz',
$re$(bar)(beque)$re$, false);
prematch | fullmatch | matches | postmatch
--+---+-+---
\N | \N| {bar,beque} | \N
(1 row)
I just changed
On Fri, 2 Feb 2007, Jeremy Drake wrote:
I just coded up for this:
CREATE FUNCTION regexp_matches(IN str text, IN pattern text) RETURNS
text[]
AS 'MODULE_PATHNAME', 'regexp_matches'
LANGUAGE C IMMUTABLE STRICT;
CREATE FUNCTION regexp_matches(
IN str text, IN pattern text
I am writing a set returning function in C. There are cases where I can
know definitively, upfront, that this function will only return one row.
I have noticed, through happenstance of partially converted function, that
I can mark a normal, non-set returning function as returning SETOF
something,
On Tue, 6 Feb 2007, Pavel Stehule wrote:
Hello,
Currently PostgreSQL support set returning functions.
ANSI SQL 2003 goes with new type of functions - table functions. With this
syntax
CREATE FUNCTION foo() RETURNS TABLE (c1 t1, ... )
PostgreSQL equal statements are:
CREATE TYPE
On Sun, 4 Feb 2007, David Fetter wrote:
On Fri, Feb 02, 2007 at 07:01:33PM -0800, Jeremy Drake wrote:
Let me know if you see any bugs or issues with this code, and I am
open to suggestions for further regression tests ;)
I have not heard anything, so I guess at this point I should figure
On Wed, 7 Feb 2007, Tom Lane wrote:
Jeremy Drake [EMAIL PROTECTED] writes:
* Put together a patch to add these functions to core. I could put them
directly in regexp.c, so the support functions could stay static. My
concern here is that I don't know if there are any functions
If I have a multi-call SRF and a user_fctx struct allocated in the
multi_call_memory_ctx, and in the if(SRF_IS_FIRSTCALL()) block while still
in the multi_call_memory_ctx I use PG_GETARG_TEXT_P(n) to get an argument
to my function, and stash the result of this in my user_fctx struct, am I
I made some notes about what you said about my patch, just so that I can
be sure that it is clear what it does.
On Sun, 11 Feb 2007, David Fetter wrote:
== PostgreSQL Weekly News - February 11 2007 ==
== Pending Patches ==
Jeremy Drake sent in a patch which implements regexp_replace
On Mon, 12 Feb 2007, Teodor Sigaev wrote:
Log Message:
---
Fix backend crash in parsing incorrect tsquery.
Per report from Jon Rosebaugh [EMAIL PROTECTED]
Is this a security issue? Does it need a new security release? I hope
that the answer is not this is contrib, it isn't as
On Tue, 13 Feb 2007, Peter Eisentraut wrote:
We don't treat crashes to be security issues of the kind that calls for
the full security exercise.
But if a security issue, by whatever definition of the term applies to
core, is found in contrib, it would result in the full security exercise,
On Mon, 12 Feb 2007, Tom Lane wrote:
Jeremy Drake [EMAIL PROTECTED] writes:
On Mon, 12 Feb 2007, Teodor Sigaev wrote:
Fix backend crash in parsing incorrect tsquery.
Is this a security issue? Does it need a new security release?
We looked at this and determined that the worst
On Sat, 24 Feb 2007, Warren Turkal wrote:
The interesting thing about Git is that is has two way sync support for a SVN
repository also. You could run a Git repository pushing changes in real time
to a SVN repository and present a CVS frontend also. I would like to try
converting the CVS
On Sat, 24 Feb 2007, Warren Turkal wrote:
On Saturday 24 February 2007 00:32, Jeremy Drake wrote:
Use cvsup, or if you don't want to go through the effort of getting that
set up, use rsync:
rsync -avzCH --delete rsync.postgresql.org::pgsql-cvs cvsroot/
Thanks
The attached sql file creates some table infrastructure and then tries to
explain a query. I get the following error on CVS HEAD:
psql:bogus_varattno_error.sql:23: ERROR: bogus varattno for OUTER var: 5
In my real data, when I attempt to run the query I get the error:
ERROR: invalid attribute
On Sun, 25 Feb 2007, Tom Lane wrote:
Jeremy Drake [EMAIL PROTECTED] writes:
psql:bogus_varattno_error.sql:23: ERROR: bogus varattno for OUTER var: 5
Any ideas what is causing this?
This looks pretty nearly related to stuff I've been hacking on recently,
so I suppose I broke something
On several occasions I have wanted to input integers in hexadecimal rather
than in decimal in PostgreSQL. I notice that there is a to_hex function,
but there is not (AFAIK) a way to provide an integer in hexadecimal.
I have written a pure-sql implementation of some functions to input
integers in
On Fri, 2 Mar 2007, Tom Lane wrote:
Jeremy Drake [EMAIL PROTECTED] writes:
On several occasions I have wanted to input integers in hexadecimal rather
than in decimal in PostgreSQL. I notice that there is a to_hex function,
but there is not (AFAIK) a way to provide an integer
On Fri, 16 Mar 2007, Andrew Dunstan wrote:
OK, for anyone that wants to play, I have created an extract that contains a
summary of every non-CVS-related failure we've had. It's a single table
looking like this:
CREATE TABLE mfailures (
sysname text,
snapshot timestamp without time
On Sun, 18 Mar 2007, Tom Lane wrote:
another icc crash|
2007-02-03 10:50:01 | 1
icc internal error |
2007-03-16 16:30:01 |29
These on mongoose are most likely a result of flaky
On Wed, 28 Nov 2012, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 11/28/2012 02:14 PM, Alvaro Herrera wrote:
Okapi has been failing sporadically on ecpg, and I wonder if it's
related to this change.
Well, it looks like the make is broken and missing a clear dependency
On Wed, 28 Nov 2012, Tom Lane wrote:
Jeremy Drake pgbuildf...@jdrake.com writes:
While we're talking about odd issues that only seem to happen on Okapi,
does anyone know of anything I can do to diagnose the pg_upgrade failure
on the 9.2 branch? There are no rogue (non-buildfarm-related
On Fri, 11 Jan 2013, Tom Lane wrote:
pgbuildf...@jdrake.com writes:
Well, that's darn interesting in itself, because the error message looks
like it should be purely a linker issue. (And I note that your other
buildfarm animal mongoose uses icc but is working anyway, so that's
definitely
On Sun, 4 Sep 2011, Tom Lane wrote:
Jeremy Drake jere...@jdrake.com writes:
I didn't see any changes that looked like they affected
CurrentMemoryContext, but I attached the compressed context diff in case
you want to look at it.
Right now I have a feeling that this is a compiler bug
On Sun, 4 Sep 2011, Tom Lane wrote:
What I would suggest is to see whether a more recent x86 version shows
the problem or not. If not, let's just write it off as an already-fixed
compiler bug.
I have installed the most recent version in the home directory of a
purpose-made user on that
On Mon, 5 Sep 2011, Bruce Momjian wrote:
Jeremy Drake wrote:
I think tomorrow I'll try to get the 9.0 compiler set up on a clean VM,
and if the issue duplicates there, I can see about setting up SSH access
if anyone is still interested in investigating this further.
What would we
101 - 138 of 138 matches
Mail list logo
