Hi,
On Tuesday 31 January 2006 18:59, you wrote:
> Shouldn't the query planner be able to do the right thing without the
> index? Where does the magic 'rows=459' come from?
ok - I've spend some time reading the postgres sources now. qesel() is using
a selectivity of DEFAULT_EQ_SEL (0.005) for all
Added to TODO:
* Allow statistics collector information to be pulled from the collector
process directly, rather than requiring the collector to write a
filesystem file twice a second?
---
Tom L
Clifford Wolf <[EMAIL PROTECTED]> writes:
> However, it would be great to have get_restriction_variable() and
> get_attstatsslot() extended so they can pass the most common values
> from the statistics cache thru expressions, as described in my earlier
> mail.
This would only be helpful if the mos
michael <[EMAIL PROTECTED]> writes:
> On Wed, 1 Feb 2006, Tom Lane wrote:
>> It's hardly a bug that you get a syntax error when $data contains
>> a single quote. It's up to you to construct a well-formed query
>> string to give to spi_exec_query, and this code is not doing that.
> As I understand
"Juan Manuel Bigi" <[EMAIL PROTECTED]> writes:
> I have executed the Grant Wizard and got:
> GRANT EXECUTE ON FUNCTION setweight(tsvector, char) TO public;
I do not know what a Functions Grant Wizard is, but your bug report
should be filed with whoever wrote that ... whoever it is, it's not
the co
"Michael Lush" <[EMAIL PROTECTED]> writes:
> CREATE OR REPLACE FUNCTION quote_bug(text) RETURNS text AS
> $$
>$data = $_[0];
>$sql = "SELECT *
> FROM test
> WHERE foo = '$data'";
>$rv_unique = spi_exec_query($sql);
It's hardly a bug that you get a syntax erro
Patrick Rotsaert <[EMAIL PROTECTED]> writes:
> on 31/01/2006 16:18 Tom Lane wrote :
>> http://www.postgresql.org/docs/8.1/static/kernel-resources.html#AEN18105
> But /proc/sys/vm/overcommit_memory reads `0', so my guess is that
> overcommit is not enabled... right?
Please read the reference I p
"Murat Tasan" <[EMAIL PROTECTED]> writes:
> During function creation, one cannot combine both SETOF and %TYPE.
Fixed here:
http://archives.postgresql.org/pgsql-committers/2006-01/msg00396.php
regards, tom lane
---(end of broadcast)-
The following bug has been logged online:
Bug reference: 2229
Logged by: Juan Manuel Bigi
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows XP proffesional
Description:Parsing error in Functions Grant Wizard
Details:
Dear people's Po
The following bug has been logged online:
Bug reference: 2228
Logged by: Michael Lush
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2 and 8.0.3
Operating system: freeBSD 4.9
Description:escaped single quotes choke spi_exec_query in plperlu
Details:
I've
The following bug has been logged online:
Bug reference: 2227
Logged by: Matthias Klein
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Windows XP
Description:Internal account lookup error
Details:
While installing PostgreSQL 8.1.2-1 on
David Fetter said:
> On Tue, Jan 31, 2006 at 08:03:41PM -0500, Bruce Momjian wrote:
>> Uh, couldn't the delimiter be a backslash in CVS mode?
>
> I don't think so. Folks?
Using backslash as a delimiter in CSV would be odd, to say the least. As an
escape char it is occasionally used, but not as a
on 31/01/2006 16:18 Tom Lane wrote :
"Patrick Rotsaert" <[EMAIL PROTECTED]> writes:
At the time of the crash, the server logs:
LOG: server process (PID 21815) was terminated by signal 9
You're running on a Linux machine with memory overcommit enabled.
Turn that off, or
The following bug has been logged online:
Bug reference: 2230
Logged by: Murat Tasan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Mac OS 10.4.4
Description:cannot return a setof column referenced types
Details:
Hi, I already heard fro
14 matches
Mail list logo
