Re: [BUGS] BUG #2225: Backend crash -- BIG table

Patrick Rotsaert wrote: > On my > system, the parameter is 0, so overcommit is *not* enabled. 0 means overcommit is enabled. You want to set it to something other than 0 to prevent overcommitting and the consequent suprising process deaths. Exactly what other values are accepted varies, but 0

Re: [BUGS] BUG #2231: Incorrect Order By

On Thu, 2 Feb 2006, Stephan Szabo wrote: > On Wed, 1 Feb 2006, Garoso, Fernando wrote: > > > > > The following bug has been logged online: > > > > Bug reference: 2231 > > Logged by: Garoso, Fernando > > Email address: [EMAIL PROTECTED] > > PostgreSQL version: 8.x > > Operating

Re: [BUGS] BUG #2231: Incorrect Order By

On Wed, 1 Feb 2006, Garoso, Fernando wrote: > > The following bug has been logged online: > > Bug reference: 2231 > Logged by: Garoso, Fernando > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.x > Operating system: GNU Linux Debian > Description:Incorrect Ord

Re: [BUGS] BUG #2225: Backend crash -- BIG table

Tom Lane wrote: 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

[BUGS] BUG #2233: Not a bug - trying to make a donation

The following bug has been logged online: Bug reference: 2233 Logged by: Peter Stys Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Operating system: MacOSX Description:Not a bug - trying to make a donation Details: This is not a bug report. PostgreSQL is

Re: [BUGS] BUG #2228: escaped single quotes choke spi_exec_query in

On Wed, 1 Feb 2006, Tom Lane wrote: > 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, an

[BUGS] PostgreSQL Windows

Hi!   I am working have a year with PostgreSQL Windows Database.   I am very happy with the Database and its looks good.   I have to report of critical bug:    I am using functions (Store procedure) to update database.   When I passing for example 20 prams' to update a database i

[BUGS] BUG #2232: Function (store procedure) prublem

The following bug has been logged online: Bug reference: 2232 Logged by: Michael Grossman Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.2 windows Operating system: windows xp q windows 2003 Description:Function (store procedure) prublem Details: Hi! I a

Re: [BUGS] BUG #2228: escaped single quotes choke spi_exec_query in

On Wed, 1 Feb 2006, Tom Lane wrote: > "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_qu

[BUGS] BUG #2231: Incorrect Order By

The following bug has been logged online: Bug reference: 2231 Logged by: Garoso, Fernando Email address: [EMAIL PROTECTED] PostgreSQL version: 8.x Operating system: GNU Linux Debian Description:Incorrect Order By Details: create table tmp ( name char(30) ); create i

Re: [BUGS] Bug in query planer ?

Clifford Wolf <[EMAIL PROTECTED]> writes: >> This would only be helpful if the most-common-values list describes >> practically all of the column population, which isn't typically the case. > Not more than it is the case already for the simple 'variable = const'. No, because while you may not kno

Re: [BUGS] Bug in query planer ?

Hi, On Wednesday 01 February 2006 18:19, you wrote: > 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