The following bug has been logged on the website:
Bug reference: 8518
Logged by: david
Email address: david.ku...@vsoftcorp.com
PostgreSQL version: 9.3.1
Operating system: Windows 7
Description:
Hi All,
I had tried using FreeBSD disk encryption but unable to find
hese cases it is the current value of a column that is needed.
So "SELECT" is read as being a top-level (as are UPDATE and DELETE) - and as
Stephen said because WHERE can be part of UPDATE and DELETE the additional
comment is made that WHERE in those contexts require "SELECT-like&quo
On Thu, Sep 26, 2013 at 4:19 PM, David Rennalls wrote:
> On Thu, Sep 26, 2013 at 3:40 PM, Kim Applegate wrote:
>> I have seen this issue on a slave although it was in version 9.2. I ran
>
> oh ok. Looks like the issue was fixed in 8.2.23 according to these
>
es, containing 4633 live
rows and 0 dead rows; 4633 rows in sample, 4633 estimated total rows
INFO: analyzing "information_schema.sql_features"
INFO: "sql_features": scanned 7 of 7 pages, containing 649 live rows
and 0 dead rows; 649 rows in sample, 649 estimated total rows
ERRO
David Fetter fetter.org> writes:
>
> Upgrade to 9.1.3 and let us know whether that fixes the problem.
I've run into this issue as well on postgres 8.4.14. Aside from upgrading to a
newer release is there any manual fixup that can be done ?
Thanks,
David
--
Sent via pgsq
Tom Lane-2 wrote
> David Johnston <
> polobo@
> > writes:
>>> Here is a minimal query that demonstrates the problem. In 9.1 it works:
>>>
>>> chris=# select * FROM current_user u join (current_user u cross join
>>> current_user v) x on true;
A much more simple example courtesy of Chris Travers from the original
-general thread that I suggested be moved to -bugs.
> Here is a minimal query that demonstrates the problem. In 9.1 it works:
>
> chris=# select * FROM current_user u join (current_user u cross join
> current_user v) x on tr
having the correct
> updated values.
> We are using default isolation level (Read Committed)
PostgreSQL 8.1 has been unsupported since 2010. Once you've upgraded
to a supported version, if the problem persists, we may be able to
help.
Cheers,
David.
--
David Fetter http://fetter.org/
f what you need to have
done. Recursion (iteration) allows you to more easily handle/walk
hierarchical data but said hierarchy remains static for the duration of the
query.
David J.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/with-recursive-ignores-side-e
e of PostgreSQL
than the one you start manually.
I am not that strong a linux user but it does seem you need to provide
considerably more detail as to your install/configuration if you expect help
resolving your issue. Specifically, HOW did you install PostgreSQL and what
configuration steps have you p
many use-cases only the single-match mode is desired.
Are there any other functions that have this same risk profile that would
increase the applicability of such a patch?
David J.
The following bug has been logged on the website:
Bug reference: 8228
Logged by: David Johnston
Email address: david.g.johns...@gmail.com
PostgreSQL version: 9.0.13
Operating system: Ubuntu Linux 10.04
Description:
The following query results in "SQL Error:
/why they can be omitted in the examples as well as
in the text - is an idea worth considering.
David J.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-8211-Syntax-error-when-creating-index-on-expression-tp5758030p5758040.html
Sent from the PostgreSQL - bug
d and basically the index is only acting as a table surrogate as
opposed to an index. If you really want to anchor the start you should
index and search on the reverse of the string so you can write it as a
postfix wildcard. The other option to index words via the full-text search
capabilities
postmaster will still shut down normally and thus release the
> shmem segment.)
>
Yup, if I attempt to start the cluster normally, it cleans up after
itself, so this is specific to --single mode.
--
David Thomas
System Engineer
EnterpriseDB - The Enterprise PostgreSQL Company
--
Sent via
The following bug has been logged on the website:
Bug reference: 7885
Logged by: David Thomas
Email address: david.tho...@enterprisedb.com
PostgreSQL version: 9.2.3
Operating system: CentOS 6.3
Description:
It seems that if the postmaster encounters a PANIC condition
*uint16* idsubst)
+matchIdSubst(LexemeInfo *stored, *uint32* idsubst)
{
bool res = true;
Kind regards.
David
On Mon, Jan 7, 2013 at 1:41 AM, Tom Lane wrote:
> dav...@gmail.com writes:
> > [ thesaurus dictionary fails for more than 64K entries ]
>
> I see a whole bunch of uses of &q
only the
offending code and whatever is minimally necessary to make it execute.
Unless the example provided is self-contained simply putting out the entire
code without any commentary makes it more difficult for people to provide
help.
David J.
--
View this message in context:
http://
;
Not A Bug.
When you add an "Order By" the resultant window FRAME is from the first record
(of the partition) up-to-and-including the current record (of the partition);
no "future" records (in the partition) are part of the window FRAME. Thus for
"last_va
? That would seem to be the area of greatest
concern - particularly around the usage of truncate/delete/drop.
Thought: would there be some way to flag a table like this to always require
the use of a schema prefix to be accessed (since right now truncated names only
have to be schema unique) in
The following bug has been logged on the website:
Bug reference: 7596
Logged by: David PEYRIERES
Email address: david.peyrie...@meteo.fr
PostgreSQL version: 9.1.4
Operating system: Red Hat
Description:
Hello.
I found a little bug in /etc/init.d/postgresql-9.x file
On Mon, Jun 11, 2012 at 06:21:43PM +0200, Magnus Hagander wrote:
> On Mon, Jun 11, 2012 at 6:14 PM, David Fetter wrote:
> > On Mon, Jun 11, 2012 at 06:04:22PM +0200, Magnus Hagander wrote:
> >> On Mon, Jun 11, 2012 at 6:01 PM, David Fetter wrote:
> >> > On Mon, Ju
On Mon, Jun 11, 2012 at 06:04:22PM +0200, Magnus Hagander wrote:
> On Mon, Jun 11, 2012 at 6:01 PM, David Fetter wrote:
> > On Mon, Jun 11, 2012 at 05:51:06PM +0200, Magnus Hagander wrote:
> >> On Mon, Jun 11, 2012 at 5:14 PM, wrote:
> >> > The following bug
On Mon, Jun 11, 2012 at 05:51:06PM +0200, Magnus Hagander wrote:
> On Mon, Jun 11, 2012 at 5:14 PM, wrote:
> > The following bug has been logged on the website:
> >
> > Bug reference: 6687
> > Logged by: David Fetter
> > Email address: da...@
The following bug has been logged on the website:
Bug reference: 6687
Logged by: David Fetter
Email address: da...@fetter.org
PostgreSQL version: 9.1.4
Operating system: All
Description:
When calling initdb -A, it is assumed--wrongly in the case of ident, that
every
Thanks guys for your prompt support!
I'm going to update Olson library on the concerned computer using the latest
files.
Thanks again.
David Chuet
Odotech inc.
-Original Message-
From: Heikki Linnakangas [mailto:heikki.linnakan...@enterprisedb.com]
Sent: May-14-12 11:51 AM
To:
Upgrade to 9.1.3 and let us know whether that fixes the problem.
Cheers,
David.
On Wed, May 02, 2012 at 09:58:16PM -0700, leo xu wrote:
> pg version is 9.1.2
>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/select-table-indicate-missing-chunk-num
me up sooner is because most Windows users either use the
'official' binaries rather than compiling from source, or link against the
dynamic runtime.
Is this something I could expect to be fixed in the near future, or is it
enough of an edge case that I should come up with some solutio
h, so please to report bugs in that
language, enlisting help wherever you need to in order to do so.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
iCal: webcal://www.tripit.com/feed/i
The following bug has been logged online:
Bug reference: 6292
Logged by: David Pinheiro
Email address: davidsantospinhe...@gmail.com
PostgreSQL version: 8.4
Operating system: Linux
Description:java.sql.PreparedStatement.setNull() throws
PSQLException
Details:
I&#
ke
precedence
configure: WARNING: ## ##
configure: WARNING: ## Report this to pgsql-bugs@postgresql.org ##
configure: WARNING: ## ##
checking for ossp/uuid.h... yes
checking whether byte ordering is bigendian... u
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Tuesday, July 26, 2011 7:42 PM
To: David Johnston
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #6131: Query Returning Incorrect Results
"David Johnston" writes:
> The embedded script exhibits
The following bug has been logged online:
Bug reference: 6131
Logged by: David Johnston
Email address: pol...@yahoo.com
PostgreSQL version: 9.0.4
Operating system: Windows 7 64-bit
Description:Query Returning Incorrect Results
Details:
The embedded script exhibits
The following bug has been logged online:
Bug reference: 6113
Logged by: David Carlos Manuelda
Email address: stormb...@gmail.com
PostgreSQL version: 9.0.4
Operating system: Gentoo Linux
Description:SET DATESTYLE='European' does not set datestyle output
The following bug has been logged online:
Bug reference: 6094
Logged by: David Hartveld
Email address: david.hartv...@mendix.com
PostgreSQL version: 9.1-beta2
Operating system: Debian GNU/Linux 6.0.2 "Squeeze"
Description:Streaming replication does not cat
o much for copying from a separate file.
>
> The attached patch seems like an appropriate fix. However, I'm
> unsure whether to apply it to released branches ... does anyone
> think this might break somebody's application?
No.
Cheers,
David.
--
David Fetter http://fe
Hola,
estoy desesperado, no consigo levantar postgresql en Opensuse, me sale el
siguiente error al intentar levantar el servicio:
psql: no se pudo conectar con el servidor: No exite el fichero o el
directorio ¿Está el servidor en ejecución localmente y aceptando conexiones
en el socket de dominio
The following bug has been logged online:
Bug reference: 6067
Logged by: David Fetter
Email address: dfet...@vmware.com
PostgreSQL version: 9.0.4
Operating system: Linux
Description:In PL/pgsql, EXISTS(SELECT ... INTO...) fails
Details:
Here's some example
at :)
> but the second case seems seriously annoying, since there's no way
> for someone to write a CTE-containing rule action without risking a
> conflict. Ideas anybody?
Is there some way to throw "not implemented" there, too? It seems to
me that making accommodations for
The following bug has been logged online:
Bug reference: 6003
Logged by: David carlos Manuelda
Email address: stormb...@gmail.com
PostgreSQL version: 9.0.3
Operating system: Gentoo Linux
Description:Cannot have a constraint foreign key on master class
with
On 03.03.2011 16:08, Robert Haas wrote:
On Tue, Feb 8, 2011 at 2:19 AM, David Schmitt wrote:
Example query:
SELECT column as zurück FROM table;
results in corruption of the "ü" (umlaut u). This causes Npgsql to fail to
match up the columns in the result set (see
http://pgf
The following bug has been logged online:
Bug reference: 5869
Logged by: David Schmitt
Email address: da...@dasz.at
PostgreSQL version: 8.4.5
Operating system: Windows 7
Description:postgresql corrupts unquoted non-ascii chars in column
aliases
Details:
Example
st noticed it quite some time
ago. Anyone got a test case that doesn't involve building PostgreSQL?
Thanks,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 5846
Logged by: David E. Wheeler
Email address: da...@kineticode.com
PostgreSQL version: 9.0.1
Operating system: Mac OS X 10.6.6
Description:Segfault Postgresql Built with --lib-libedit-preferred
Details
some kind of plans to build major version
upgrades into your development process, as end-of-life is a fact of
life in this as in every other software or system.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter
The following bug has been logged online:
Bug reference: 5836
Logged by: David Pinheiro
Email address: davidsantospinhe...@gmail.com
PostgreSQL version: 8.4
Operating system: Centos
Description:Enum Support Functions don't work on empty tables
Details:
The following bug has been logged online:
Bug reference: 5775
Logged by: David Quinn-Jacobs
Email address: d...@ecornell.com
PostgreSQL version: 9.0.1
Operating system: Cent OS 5
Description:DBLINK Connection String Truncation
Details:
Causes connection failure
On Mon, Nov 15, 2010 at 06:55:47PM -0500, Tom Lane wrote:
> "David Fetter" writes:
> > CREATE SEQUENCE my_seq;
> > WITH t AS (SELECT nextval('my_seq')) VALUES(1);
> > SELECT currval('my_seq');
>
> > ERROR: currval of sequence &
The following bug has been logged online:
Bug reference: 5754
Logged by: David Fetter
Email address: da...@fetter.org
PostgreSQL version: 8.4+
Operating system: All
Description:CTE optimization fails to account for side effects
Details:
Here's how to repr
ress
Date: Thu, 14 Oct 2010 10:44:50 +0900
From: Itagaki Takahiro
To: David Newall, PostgreSQL Hackers
CC: pgsql-bugs@postgresql.org
On Mon, Oct 11, 2010 at 7:42 AM, David Newall
wrote:
Trivial program to demonstrate problem:
main() {
ECPGdebug(1,stderr);
exec sql
On 14/10/10 12:14, Itagaki Takahiro wrote:
Which solution is better? Or, another idea?
This does seem to be an new bug in previously working code. While any
solution that fixes the problem is good, it might pay to look the code
that worked before. As reported, it worked for ecpg (Postgr
6.32-24-generic #43-Ubuntu SMP Thu Sep 16 14:58:24 UTC
2010 x86_64 GNU/Linux
Two cores
This appears to be a regression; it doesn't occur with ecpg (PostgreSQL
8.3.8) 4.4.1
Regards,
David
--
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/23/2010 9:53 PM, Tom Lane wrote:
David Schmitt writes:
Executing the attached example.sql on a fresh database demonstrates the
problem I'm seeing:
Found it. If you need a patch right away, it's a one-liner:
diff --git a/src/backend/optimizer/path/allpaths.c
b/src/backend
On 9/23/2010 5:33 PM, Tom Lane wrote:
"David Schmitt" writes:
Description:Optimizer creates strange execution plan leading to
wrong results
Please supply a self-contained example demonstrating the incorrect results.
The information you've provided is completely
The following bug has been logged online:
Bug reference: 5673
Logged by: David Schmitt
Email address: da...@dasz.at
PostgreSQL version: 8.4.4
Operating system: Windows 7
Description:Optimizer creates strange execution plan leading to
wrong results
Details
d.
> >
> Thanks, I will do that. However, I cannot call myself a hacker, I
> am but a mere beginner with Postgres.
You're a hacker when you start hacking :)
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfet
with 140,000,000 rows.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Tuesday, September 07, 2010 11:17 PM
To: David Platt
Cc: 'Bruce Momjian'; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #5642: pg_upgrade does not handle shared libraries
for language handlers
.
-Original Message-
From: Bruce Momjian [mailto:br...@momjian.us]
Sent: Tuesday, September 07, 2010 9:54 PM
To: David Platt
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #5642: pg_upgrade does not handle shared libraries
for language handlers
David Platt wrote:
>
> The following b
documentation indicated that the path to the shared library had to be
declared because I don't remember any example showing $library.
-Original Message-
From: Bruce Momjian [mailto:br...@momjian.us]
Sent: Tuesday, September 07, 2010 10:30 PM
To: Tom Lane
Cc: David Platt; pgsql
The following bug has been logged online:
Bug reference: 5647
Logged by: David Sahagian
Email address: david.sahag...@gmail.com
PostgreSQL version: 9.0 beta4
Operating system: win XP
Description:COPY TO does not respect the
[standard_conforming_strings] setting
The following bug has been logged online:
Bug reference: 5642
Logged by: David Platt
Email address: davidpl...@davidplatt.com
PostgreSQL version: 9.0 RC1
Operating system: CentOS 5.5
Description:pg_upgrade does not handle shared libraries for language
handlers
|19 |
readline_echoing_p
[866] |22165210|0010|OBJT |GLOB |0|19 |
rl_readline_name
On Aug 27, 2010, at 9:38 PM, Tom Lane wrote:
"David Kensiski" writes:
The psql binary (64-bit from binary install) dumps core when I
attempt to
edit the input line after a few
The following bug has been logged online:
Bug reference: 5631
Logged by: David Kensiski
Email address: da...@schoolloop.com
PostgreSQL version: 8.4
Operating system: Solaris 10
Description:psql dumps core during command editing
Details:
The psql binary (64-bit from
The following bug has been logged online:
Bug reference: 5616
Logged by: David E. Wheeler
Email address: da...@kineticode.com
PostgreSQL version: 8.4
Operating system: Mac OS X 10.6.4
Description:psql Doesn't Change Log files on \c
Details:
I have this
On Aug 5, 2010, at 12:16 PM, Tom Lane wrote:
> HINT: No aggregate function matches the given name and argument
> types. Perhaps you misplaced ORDER BY; ORDER BY must appear after all
> regular arguments of the aggregate.
+1
David
--
Sent via pgsql-bugs mailing list (p
> Well, maybe we need to expend some more sweat on the error message then.
> But this patch was still a prerequisite thing, because without it there
> is no error that we can complain about.
Yeah, understood.
Best,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
> What function name do you believe was called?
The message says:
string_agg(f1 order by f1, ',')
That looks like string_agg(text, text) or string_agg(anyelement, text).
Best,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
(I don't think it's practical to get the HINT to
> read "Put the ORDER BY at the end" ;-)) but at least it should
> get people pointed in the right direction when they do this.
It confuses the shit out of me. It says "string_agg(text)" doesn't exist when
gates, or at least never have any built-in ones
> that use such a feature.
>
> By my count the following people had offered an opinion on making
> this change:
> for: tgl, josh, badalex, mmoncure
> against: rhaas, thom
> Anybody else want to vote, or change their
;) People who have been
> waiting for this will burn me as a heretical witch... er.. man
> witch... warlock?
Witch.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
iCal: webcal://
On 7/9/2010 4:53 PM, Tom Lane wrote:
"David Schmitt" writes:
This is not implemented:
DECLARE
working_cursor NO SCROLL CURSOR FOR EXECUTE $$SELECT something $$ || tbl
|| $$ ... $$;
What's wrong with OPEN FOR EXECUTE?
The proposed addition seems a bit weird anyway si
The following bug has been logged online:
Bug reference: 5549
Logged by: David Schmitt
Email address: da...@dasz.at
PostgreSQL version: 8 and 9
Operating system: n/a
Description:Feature: plpgsql should allow DECLARE cursor FOR EXECUTE
'...'
Details:
T
Thanks, was able to rebuild plpython.so and it works.
Also mapping SQL Arrays to Python lists is awesome.
On 06/09/2010 09:05 PM, Tom Lane wrote:
"David Gardner" writes:
Description:plpythonu gives cache lookup error
Fixed, thanks for
The following bug has been logged online:
Bug reference: 5497
Logged by: David Gardner
Email address: dgard...@creatureshop.com
PostgreSQL version: 9.0beta2
Operating system: Debian Linux
Description:plpythonu gives cache lookup error
Details:
hdpsdb=# CREATE OR
>
> Even if we quote them in the dump, I assume applications would need
> to quote them too, which I doubt many do.
It seems like something that's doable by pg_dump as a "default off"
option. TODO for 9.1?
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415
The following bug has been logged online:
Bug reference: 5463
Logged by: David Orr
Email address: david_or...@hotmail.com
PostgreSQL version: 8.3.11 or 8.4.4
Operating system: Windows 7 Starter
Description:incorrect password when downloading/installing
Details:
I
27;s more consistent
about the use of reserved words.
Best,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
an actually doing what Michael would like.
Yes, I suspect that he can solve his problem by adding the iss schema to
search_path.
Best,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
#x27; and statecode = 'FL';
>
> However this does work
>
> Select citystateinfoid from iss.citystateinfo where cityname =
> 'Jacksonville' and statecode = 'FL'
>
> The second query is how the data is actually stored. I've already forwarded
> our
uot; or run initdb with an argument other than "../data".
The first part of this sentence is what I attempted to do, and it did not
work.
Regards,
David
On Fri, Feb 26, 2010 at 16:52, Tom Lane wrote:
> "David Andersen" writes:
> > [ initdb fails with ]
> >
The following bug has been logged online:
Bug reference: 5347
Logged by: David Andersen
Email address: david.ander...@andersen-innovation.com
PostgreSQL version: 8.4.2
Operating system: Windows 7 64-bit
Description:initdb does not work when a data directory has been
okay tradeoff to get recursive calls working again,
but I certainly hope that Safe can be updated in the near future to give us
both.
There seem to be no good answers here.
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
y adding the extra security when *not* under threads as well?
I find this all very confusing, frankly.
Best,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
cant speed boost.
That solves the problem with recursion or with $a and $b or both?
I'm happy to rebuild Perl without threads, since I'm not going to use Padre
after all. But that won't help the millions who rely on package-supplied Perls,
which are nearly always threaded AFAICT.
you said :) ). Ill see if I can figure something out via straight
> Safe tonight.
I think Tom meant, what sorts of changes to PostgreSQL do you think might solve
the problem?
Best,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
okay tradeoff to get recursive calls working again,
but I certainly hope that Safe can be updated in the near future to give us
both.
There seem to be no good answers here.
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
7;s the understatement of the month. What you're saying, IIUC, is
> that if function A calls function B via a SPI command, and B wasn't
> executed previously in the current session, it would fail? Seems
> entirely unacceptable.
Exactly what I was thinking. This "fix" is
read? I may have inadvertently used some
> bash/gnu-isms... sorry about that.
>
> *** a/configure
> --- b/configure
Edit configure.in, not configure :)
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: dav
time the C code looks up the utf8::SWASHNEW method without a problem.
Oh, so 2.19 is less secure in that regard, yes?
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
able way to fix Safe such that PostgreSQL would work without
> changes.
Hrm. I don't have this bug with Safe 3.19, FWIW.
Best,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
the short run, you can downgrade to Safe.pm 2.19 and the problem will go
away. Or just use PL/Perlu, which doesn't rely on Safe.pm.
Best,
David
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Found in 8.4.2, replicated in HEAD. Steps:
1. Create PL/Perl function.
2. Run it.
3. Create same function with PL/PerlU
4. Run it.
5. Create same function again with PL/Perl
6. Boom.
Example on HEAD built today (ignore the error from the plperl version, that's
the issue I'm trying to fix locally
The following bug has been logged online:
Bug reference: 5259
Logged by: David
Email address: goodom...@21cn.com
PostgreSQL version: 8.0
Operating system: RHEL5
Description:the table name double
Details:
hi
the table name double,why
t report them here; please report to those
> projects directly. Alternatively you can look at the available href='/community/lists'>mailing lists and see if there is a more
> apropriate list available."
This is better than what I sent :)
Cheers,
David.
--
David Fetter http
oblems with
the PostgreSQL database, for problems with database connectors like
JDBC and ODBC, graphical administration tools like pgAdmin and
phpPgAdmin, or other external projects like Slony, Bucardo, etc.,
please report to them directly. In cases where you have a problem
with things outside
The following bug has been logged online:
Bug reference: 5240
Logged by: David Gardner
Email address: dgard...@creatureshop.com
PostgreSQL version: 8.4.1
Operating system: Debian Linux, amd64 2.6.30
Description:Stable Functions that return a table type with a dropped
:
CREATE OR REPLACE FUNCTION pyreplacenoreassign(src text, s text)
RETURNS text AS
$BODY$
return src.replace(s,'')
$BODY$
LANGUAGE 'plpythonu' VOLATILE
COST 100;
ALTER FUNCTION pyreplacenoreassign(text, text) OWNER TO dgardner;
Tom Lane wrote:
"David Gardner" writ
The following bug has been logged online:
Bug reference: 5232
Logged by: David Gardner
Email address: dgard...@creatureshop.com
PostgreSQL version: 8.4.1
Operating system: Debian, amd64
Description:plpythonu s=s.op() raises an exception
Details:
If I create the
The following bug has been logged online:
Bug reference: 5161
Logged by: christian david
Email address: chrisdav8...@hotmail.com
PostgreSQL version: 08_02_0400
Operating system: windows xp
Description:tome nota del siguiente error un error ha ocurrido 999
Details
braic numbers, of which rational numbers are a proper
subset, is countable and hence has Lebesgue measure zero on the real
line.
;)
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
1 - 100 of 303 matches
Mail list logo
