On Fri, Mar 26, 2010 at 7:00 AM, Dimitri Fontaine
dfonta...@hi-media.com wrote:
Timothy Seever tim.see...@gmail.com writes:
CREATE FUNCTION testfunc() RETURNS setof tablec AS $BODY$ SELECT * FROM
tablec; $BODY$ LANGUAGE 'sql' STABLE;
Common wisdom saith to never ever use SELECT * in your
On Tue, Mar 16, 2010 at 3:06 AM, beulah prasanthi itsbeu...@gmail.com wrote:
i deleted DB and created new DB when i execute my queries i got the
following error.please help me
could not load library C:/Program Files/PostgreSQL/8.4/lib/pldbgapi.dll:
The specified module could not be found
On Tue, Mar 16, 2010 at 7:02 AM, Peter Eisentraut pete...@gmx.net wrote:
On mån, 2010-03-15 at 14:13 -0700, Josh Berkus wrote:
1. Create a function.
2. In one session, start an explicit transaction.
3. Do a CREATE OR REPLACE on the same function, but do not commit.
4. Open a 2nd session, and
On Mon, Mar 15, 2010 at 3:04 PM, Gregg Lind gregg.l...@gmail.com wrote:
As per http://osdir.com/ml/pgsql-hackers/2010-03/msg00331.html, I would
certainly find it helpful is count(distinct(myfield)) wasn't a full index
scan.
We should maybe add this to our Todo file, if it's not there already
On Thu, Mar 4, 2010 at 5:55 AM, ALEX bav...@mail.ru wrote:
The following bug has been logged online:
Bug reference: 5362
Logged by: ALEX
Email address: bav...@mail.ru
PostgreSQL version: 8.3
Operating system: linux ubuntu 9.10 server
Description: WARNING could
On Fri, Mar 12, 2010 at 4:59 AM, Igor Moiseev moiseev.i...@gmail.com wrote:
Thank you Bruce! This solution is even more flexible!
But how is it possible to know if the docs gives almost nothing
http://search.postgresql.org/search?u=/docs/8.4/static/q=psqlrc
The first of those two hits is an
On Thu, Mar 11, 2010 at 11:59 AM, Alexey mansell...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5371
Logged by: Alexey
Email address: mansell...@gmail.com
PostgreSQL version: 8.4
Operating system: Windows XP Pro
Description: Error
On Fri, Mar 5, 2010 at 5:24 AM, Markus Wichitill ma...@gmx.de wrote:
The following bug has been logged online:
Bug reference: 5364
Logged by: Markus Wichitill
Email address: ma...@gmx.de
PostgreSQL version: 8.4.2
Operating system: Linux, Win7
Description:
On Mon, Mar 8, 2010 at 5:19 AM, Savita savita.ha...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5365
Logged by: Savita
Email address: savita.ha...@gmail.com
PostgreSQL version: 8.3.5
Operating system: SunOS 5.10 Generic_139555-08 sun4u
On Thu, Mar 11, 2010 at 8:50 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Robert Haas escribió:
On Fri, Mar 5, 2010 at 8:09 AM, Tom Lane t...@sss.pgh.pa.us wrote:
What I'd be for is breaking the docs out as a separate top-level target,
ie make docs, make install-docs. I don't much
On Tue, Mar 9, 2010 at 11:02 AM, Tom Lane t...@sss.pgh.pa.us wrote:
We may need to document it, but not like that; it's (a) incorrect and
(b) unhelpful to the reader, who is left without any clear idea of what
to avoid. I think that the real issue here doesn't have anything to do
with NEW/OLD
On Sun, Mar 7, 2010 at 12:08 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Mar 5, 2010 at 5:32 PM, Tom Lane t...@sss.pgh.pa.us wrote:
It's arguably a bug, but since we lack consensus on whether NULL and
ROW(NULL,NULL,...) are the same thing, it's
On Fri, Mar 5, 2010 at 8:09 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Peter Eisentraut pete...@gmx.net writes:
On tor, 2010-03-04 at 17:53 +, Lou Picciano wrote:
./configure --no-docs or ./configure --with-htmldocs-only
But that would be a negative regression for end users, who we want to
On Fri, Mar 5, 2010 at 9:21 AM, Peter Eisentraut pete...@gmx.net wrote:
By splitting out the doc building into a separate target, we will have
less users installing the documentation.
I don't see why. And even if it's true, it just means some people
were installing the docs by accident before
On Fri, Mar 5, 2010 at 3:52 AM, Thomas Kellerer
bestell...@kellerer.name wrote:
Thanks for the feedback.
Is the problem specific to 8.4.2 or to the Windows platform (or both)?
Neither, actually.
...Robert
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to
2010/3/3 Oleg Serov sero...@gmail.com:
I'm asking to fix this =)
On Wed, Mar 3, 2010 at 9:53 PM, Robert Haas robertmh...@gmail.com wrote:
It does seem weird that assigning NEW to var changes the value; I'm
not sure why that happens. Is that what you're asking about?
Anyone else have
On Fri, Mar 5, 2010 at 5:32 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Mar 3, 2010 at 9:53 PM, Robert Haas robertmh...@gmail.com wrote:
It does seem weird that assigning NEW to var changes the value; I'm
not sure why that happens. Is that what
On Thu, Mar 4, 2010 at 9:15 AM, Peter Eisentraut pete...@gmx.net wrote:
On ons, 2010-02-24 at 12:16 -0500, Tom Lane wrote:
Joe Conway m...@joeconway.com writes:
Related to this I have noticed in recent weeks on my own development
machine that make install takes *much* longer, but only
On Wed, Mar 3, 2010 at 8:48 AM, Gurjeet Singh singh.gurj...@gmail.com wrote:
On Wed, Mar 3, 2010 at 8:37 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Mar 3, 2010 at 7:29 AM, Gurjeet Singh singh.gurj...@gmail.com
wrote:
I just realized that it is the subquery pull-up that is leading
On Wed, Mar 3, 2010 at 7:29 AM, Gurjeet Singh singh.gurj...@gmail.com wrote:
I just realized that it is the subquery pull-up that is leading to this
problem, not predicate push-down. Sleeping over it does really help I guess
:)
So instead of the LIMIT 1000, OFFSET 0 clause is the right choice
2010/3/3 Oleg Serov sero...@gmail.com:
2010/3/1 Robert Haas robertmh...@gmail.com
It's not obvious whether this is the same as one of the various other
problems you've complained about. If it isn't, an English description
of what you think the problem is would probably improve your odds
On Fri, Feb 26, 2010 at 1:49 AM, Toni Helenius
toni.helen...@syncrontech.com wrote:
I did supply it? As cvs-attachment. I'll attach it again with txt-extension.
I tried to reproduce this too with Windows XP 32-bit, Windows 2003 64-bit.
And I couldn't. Of course I didn't find a Windows 2008
It's not obvious whether this is the same as one of the various other
problems you've complained about. If it isn't, an English description
of what you think the problem is would probably improve your odds.
See also:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
...Robert
Just to save anyone else reading through these the time it took for me
to figure this out, this was resubmitted as bug #5353, and Tom replied
to that one.
...Robert
2010/2/26 Oleg Serov sero...@gmail.com:
Hello!? anybody will fix this bug? Hey!
On Mon, Feb 23, 2009 at 5:11 PM, Oleg
On Mon, Mar 1, 2010 at 10:52 AM, Vitali vit...@lumensoftware.com wrote:
The following bug has been logged online:
Bug reference: 5354
Logged by: Vitali
Email address: vit...@lumensoftware.com
PostgreSQL version: 8.1.x 8.2.x
Operating system: Windows, Linux
On Thu, Feb 25, 2010 at 1:58 AM, Toni Helenius
toni.helen...@syncrontech.com wrote:
I reindexed everything and vacuumed. The system tables and our tables. It
didn't work. I get the following:
pg_dump: finding the columns and types of table bsc_day1_001
pg_dump: finding default expressions
2010/2/25 Oleg Serov sero...@gmail.com:
Thanks!, when it will be released on 8.3.X?
Looks like the last set of back-branch releases was wrapped 12/10/09,
the set before that on 9/4/09, and the previous set on 3/13/09 (but
there was a major release in the mix there). So I'd guess we're
getting
On Tue, Feb 23, 2010 at 5:43 PM, Simon Ng simon94...@yahoo.com wrote:
The following bug has been logged online:
Bug reference: 5344
Logged by: Simon Ng
Email address: simon94...@yahoo.com
PostgreSQL version: 8.1.11
Operating system: RedHat Linux
Description:
On Wed, Feb 17, 2010 at 1:06 PM, Ben Chobot be...@silentmedia.com wrote:
- Hash (cost=153.63..153.63 rows=2178408 width=4) (actual
time=0.207..0.207 rows=1 loops=1)
- Nested Loop (cost=4.58..153.63 rows=2178408 width=4)
(actual time=0.203..0.204 rows=1 loops=1)
On Fri, Feb 12, 2010 at 5:04 AM, Alexey Klyukin al...@commandprompt.com wrote:
On Feb 12, 2010, at 6:21 AM, Robert Haas wrote:
On Thu, Feb 11, 2010 at 10:47 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Feb 11, 2010 at 3:12 PM, Alexey Klyukin al...@commandprompt.com
wrote:
I think
On Thu, Feb 11, 2010 at 11:45 PM, sourabh bansal
sourabh.k.ban...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5324
Logged by: sourabh bansal
Email address: sourabh.k.ban...@gmail.com
PostgreSQL version: 8.4
Operating system: windows XP SP2
On Thu, Feb 11, 2010 at 11:25 AM, Robert Haas robertmh...@gmail.com wrote:
I can see VACUUM making VACUUM FULL faster. I don't think VACUUM FULL
should make VACUUM FULL ANALYZE faster.
Err, let me correct myself. A second VACUUM FULL should be faster
than the first one. But the two together
On Wed, Feb 10, 2010 at 8:56 AM, Eric Pailleau e...@numlog.fr wrote:
The following bug has been logged online:
Bug reference: 5322
Logged by: Eric Pailleau
Email address: e...@numlog.fr
PostgreSQL version: 8.2.3
Operating system: linux debian
Description: Time
On Thu, Feb 11, 2010 at 1:44 PM, Dave Olszewski cx...@pobox.com wrote:
The following bug has been logged online:
Bug reference: 5323
Logged by: Dave Olszewski
Email address: cx...@pobox.com
PostgreSQL version: 8.3.9
Operating system: Linux
Description: plperl
On Thu, Feb 11, 2010 at 3:12 PM, Alexey Klyukin al...@commandprompt.com wrote:
I think this might be the same problem previously discussed here:
http://archives.postgresql.org/pgsql-bugs/2010-01/msg00224.php
Seems to be the same problem. Backtrace I'm getting on 8.4 is almost
identical to
On Thu, Feb 11, 2010 at 10:47 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Feb 11, 2010 at 3:12 PM, Alexey Klyukin al...@commandprompt.com
wrote:
I think this might be the same problem previously discussed here:
http://archives.postgresql.org/pgsql-bugs/2010-01/msg00224.php
Seems
On Sun, Feb 7, 2010 at 12:00 AM, Josh Berkus j...@agliodbs.com wrote:
On 2/6/10 8:20 PM, Robert Haas wrote:
On Sat, Feb 6, 2010 at 7:43 PM, The Fuzzy Chef fu...@fuzzychef.org wrote:
It's too bad you didn't capture a stack backtrace at step #3 or step
#6. If you manage to reproduce the problem
On Sun, Feb 7, 2010 at 8:03 PM, Michail Antonov atin65...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5319
Logged by: Michail Antonov
Email address: atin65...@gmail.com
PostgreSQL version: 8.4.2
Operating system: Windows XP
Description:
On Fri, Feb 5, 2010 at 6:25 PM, Marc rasck...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5317
Logged by: Marc
Email address: rasck...@gmail.com
PostgreSQL version: 8.4.2-1
Operating system: windows xp
Description: no puedo
On Thu, Feb 4, 2010 at 8:38 AM, Cristian Bittel cbit...@gmail.com wrote:
2010/2/3 Robert Haas robertmh...@gmail.com
So you're saying that if pgadmin is open when you close the terminal
services session, the SERVER crashes?
Did you somehow start the server in that same session
On Fri, Feb 5, 2010 at 9:50 PM, The Fuzzy Chef fu...@fuzzychef.org wrote:
Just had a very odd thing happen with an 8.4.2 database, and am
concerned it's an undiagnosed bug:
(1) created and dropped the same database 10-15 times in the course of
running some tests.
(2) at one point, dropdb
On Wed, Feb 3, 2010 at 2:13 PM, Kelly SACAULT kelly.saca...@gmail.com wrote:
Here is what I read from the officiel manual :
http://www.postgresql.org/docs/8.0/static/sql-syntax.html
stating that :
.. Identifier and key word names are case insensitive...
This is not the truth at all and I
On Mon, Feb 1, 2010 at 11:28 AM, Cristian cbit...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5305
Logged by: Cristian
Email address: cbit...@gmail.com
PostgreSQL version: 8.3.9
Operating system: Windows 2003 Server Standard x64
On Wed, Feb 3, 2010 at 9:32 PM, Dan Baldev dbal...@msn.com wrote:
The following bug has been logged online:
Bug reference: 5312
Logged by: Dan Baldev
Email address: dbal...@msn.com
PostgreSQL version: 8.4
Operating system: Windows Vista
Description: I NEED HELP
On Wed, Feb 3, 2010 at 9:46 PM, Daniel J. Baldev dbal...@msn.com wrote:
All I want to do is to delete a database, but I don't know how to actually
input the dropdb command and what other stuff I need to open...can you help?
I think my problem will be very simple for someone who understands this
On Sun, Jan 31, 2010 at 9:07 AM, Steve White swh...@aip.de wrote:
Hi,
I'm aware that this is a manifestation of the problem mentioned in the
Caveats subsection of the Inheritance section. I want to emphasize it,
and maybe rattle your cage a bit.
I find the Postgres notion of inheritance
On Fri, Jan 29, 2010 at 11:02 AM, Fujii Masao masao.fu...@gmail.com wrote:
You seem to focus on the above trouble. I think that this happened because
recovery.conf was deleted and restore_command was not given. In fact, the
WAL file (e.g., pg_xlog/00023C8200A3) required for recovery
On Fri, Jan 29, 2010 at 3:32 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Actually, I think there's a tiny harmless bug in the server too. When it
prints the error message:
2010-01-18 21:08:31 UTC ()FATAL: could not restore file
00023C8200D8 from archive:
On Tue, Jan 26, 2010 at 1:11 PM, Juergen Weber webe...@gmail.com wrote:
An XATMI C API should be added to the PostgresQL C client, so one could run
XA transactions under control of a TX monitor. An interesting usecase would
be to use PostgresQL together with the LGPL open source JBoss Blacktie
On Mon, Jan 18, 2010 at 5:13 AM, heyong hewy...@126.com wrote:
The following bug has been logged online:
Bug reference: 5285
Logged by: heyong
Email address: hewy...@126.com
PostgreSQL version: postgresql-8.3
Operating system: solarias
Description:contrib\xml2
On Mon, Jan 18, 2010 at 6:03 AM, G.Schaeffler s...@sie.at wrote:
The following bug has been logged online:
Bug reference: 5286
Logged by: G.Schaeffler
Email address: s...@sie.at
PostgreSQL version: 8.4.2
Operating system: windows server 2003 std
Description:
On Mon, Jan 18, 2010 at 12:43 AM, azuneko azun...@hotmail.com wrote:
The following bug has been logged online:
Bug reference: 5284
Logged by: azuneko
Email address: azun...@hotmail.com
PostgreSQL version: 8.3.3
Operating system: FreeBSD7.0.2
Description:
On Tue, Jan 12, 2010 at 8:04 AM, Thomas Specker
gradgis.spec...@bluewin.ch wrote:
Hi all
after a long time of trying to install PostgreSQL with ...
Computer:
- Windows2000 (Jurassic Parc, I know ...)
- PostGreSQL 8.3.9 and msi-file
or PostGreSQL 8.4.2 and one click installer
- Data
On Tue, Jan 12, 2010 at 7:45 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Vee se...@hotmail.com writes:
-- The problem query
select data, regexp_matches(data, '(h..l)')
from test;
hello {hell}
Since I have no where clause, I would expect to see all the rows in the
result of the second
On Mon, Jan 11, 2010 at 11:41 AM, Steve White swh...@aip.de wrote:
I see nothing in the documentation about this
http://www.postgresql.org/docs/8.4/static/plpython.html
It only talks about passing composite types into and out of functions.
This is an unpleasant discovery for those
On Sun, Jan 10, 2010 at 10:22 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Error : could not open server file C:\\My Pictures\\sample.jpg
No such file or directory
Anyway, do you have standard_conforming_strings turned on?
Good question. Another thought would be whether the OP is
On Wed, Jan 6, 2010 at 11:13 PM, Mike Landis mlan...@pnmx.com wrote:
Can you please stop displaying the email addresses on bug reports? It's one
thing to require an email address - it's another thing entirely to publish
it for spam address harvesting bots.
This is an example page...
On Thu, Jan 7, 2010 at 9:16 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Robert Haas escribió:
On Wed, Jan 6, 2010 at 11:13 PM, Mike Landis mlan...@pnmx.com wrote:
Can you please stop displaying the email addresses on bug reports? It's
one
thing to require an email address - it's
On Thu, Jan 7, 2010 at 10:00 AM, Michael Felt mamf...@gmail.com wrote:
mich...@x054:[/data/prj/postgresql-8.4.2/src]grep cwd */*.c
Well, unless you redefine it...
port/exec.c:#define getcwd(cwd,len) GetCurrentDirectory(len, cwd)
If you look at the context of this #define you'll see that it
On Thu, Jan 7, 2010 at 7:51 AM, Mike Landis mlan...@pnmx.com wrote:
Try the following, where mystring is an extension of std::string...
It seems to me this would be a lot easier if you could attach a
complete program that someone could just compile, instead of code
fragments that are missing
On Thu, Jan 7, 2010 at 11:39 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I have to say that the error message that is produced by the above
test case could easily send one looking in the wrong direction, and
could perhaps stand to be improved. Could we
On Thu, Jan 7, 2010 at 7:31 PM, Mark Kirkwood
mark.kirkw...@catalyst.net.nz wrote:
Mike Landis wrote:
Pick a database and table that exists, configure the string cconstants,
compile and run the attached cpp, get 0 instead of 1 (that you get in
pgAdmin...
Where's can I download the libpq
2010/1/2 Tomas Studva tstu...@gmail.com:
Hi all gurus,
I've encountered on my computer this bug. I will try to describe all what I
have discovered till now.
1, this bug happened a few times before and wasn't resolved:
bug 5130 -
On Mon, Jan 4, 2010 at 5:29 AM, Toni Helenius
toni.helen...@syncrontech.com wrote:
The following bug has been logged online:
Bug reference: 5260
Logged by: Toni Helenius
Email address: toni.helen...@syncrontech.com
PostgreSQL version: 8.3.9
Operating system: Windows
On Sun, Jan 3, 2010 at 10:48 PM, Ben Woosley ben.woos...@gmail.com wrote:
Check constraints successfully accept columns named with reserved words when
they are qualified by table using the . syntax, e.g. check (mod(table.as,
2) = 0)
However, unique and foreign key constraints added using the
On Mon, Jan 4, 2010 at 8:44 AM, Takesver Kumar Thakur
takesver.tha...@mobilefundas.com wrote:
The following bug has been logged online:
Bug reference: 5261
Logged by: Takesver Kumar Thakur
Email address: takesver.tha...@mobilefundas.com
PostgreSQL version: postgresql-8.1
On Wed, Dec 30, 2009 at 7:36 AM, Gaurav K Srivastav gaurav...@gmail.com wrote:
Sorry Craig,
I am using
PostgreSQL 8.3.8 on i686-redhat-linux-gnu, compiled by GCC gcc (GCC) 3.4.6
20060404 (Red Hat 3.4.6-10)
version. and in my case I have to drop database and recreate it without
stop/restart
On Mon, Dec 21, 2009 at 7:05 AM, Ashish Anand ashish.the@gmail.com wrote:
Hi,
I downloaded from here
http://www.postgresql.org/download/windows
which leads to
http://www.enterprisedb.com/products/pgdownload.do#windows
and has a note:
The one click installer is maintained by Dave Page at
On Thu, Dec 17, 2009 at 4:06 PM, Ashish Anand ashish.the@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5250
Logged by: Ashish Anand
Email address: ashish.the@gmail.com
PostgreSQL version: 8.4.1
Operating system: Windows 7
On Wed, Dec 16, 2009 at 1:14 PM, David Lerner
ll014n1...@blueyonder.co.uk wrote:
The following bug has been logged online:
Bug reference: 5247
Logged by: David Lerner
Email address: ll014n1...@blueyonder.co.uk
PostgreSQL version: 8.3.9.9343
Operating system: windows
On Wed, Dec 16, 2009 at 4:35 AM, Stefan Kaltenbrunner
ste...@kaltenbrunner.cc wrote:
updated the website with that wording - should be up on the next site
reload.
Thanks!
...Robert
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
On Tue, Dec 15, 2009 at 11:18 PM, Philip Graham phi...@lightbox.org wrote:
Robert Haas wrote:
On Mon, Dec 14, 2009 at 11:15 PM, Philip Graham phi...@lightbox.org
wrote:
The following bug has been logged online:
Bug reference: 5244
Logged by: Philip Graham
Email address
On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagander mag...@hagander.net wrote:
On Wed, Dec 16, 2009 at 16:12, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Alexey Luchko wrote:
postgres.exe!mdpostckpt+0x181b38
postgres.exe!mdpostckpt+0x18bbdb
This stack
On Wed, Dec 16, 2009 at 11:05 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Robert Haas escribió:
We should really take some of the vast quantity of really useful
information that is in the wiki and try to index it somehow or
incorporate it into the docs. I'm always learning about new
On Mon, Dec 14, 2009 at 10:06 PM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Dec 14, 2009 at 12:59 PM, Robert Haas robertmh...@gmail.com wrote:
The new explain formats break if you have a multi-query statement.
I will fix this, unless someone else beats me to it.
Proposed patch attached
On Wed, Dec 16, 2009 at 9:03 PM, Craig Ringer
cr...@postnewspapers.com.au wrote:
On 16/12/2009 11:55 PM, Robert Haas wrote:
On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagandermag...@hagander.net
wrote:
On Wed, Dec 16, 2009 at 16:12, Tom Lanet...@sss.pgh.pa.us wrote:
Alvaro Herreraalvhe
On Tue, Dec 15, 2009 at 12:09 AM, Craig Ringer
cr...@postnewspapers.com.au wrote:
On 15/12/2009 12:35 PM, Mark Williamson wrote:
So what happened is, the above update never completed and the Postgresql
service consumed all available memory. We had to forcefully reboot the
machine
That
On Tue, Dec 15, 2009 at 11:02 AM, Greg Stark gsst...@mit.edu wrote:
On Tue, Dec 15, 2009 at 3:44 PM, Robert Haas robertmh...@gmail.com wrote:
This is an
issue that other people have run into in the past, and I don't think
we have a good solution. I wonder if we should put some kind
On Mon, Dec 14, 2009 at 11:15 PM, Philip Graham phi...@lightbox.org wrote:
The following bug has been logged online:
Bug reference: 5244
Logged by: Philip Graham
Email address: phi...@lightbox.org
PostgreSQL version: 8.3.8
Operating system: Linux
Description:
On Tue, Dec 15, 2009 at 12:07 PM, Greg Stark gsst...@mit.edu wrote:
On Tue, Dec 15, 2009 at 4:16 PM, Robert Haas robertmh...@gmail.com wrote:
I didn't know that, but it I think by the time malloc returns 0
usually other bad things are happening. I don't think that's really
an answer.
Only
On Mon, Dec 14, 2009 at 2:57 AM, Gerhard Lutz
gerhard.l...@mbtech-group.com wrote:
The following bug has been logged online:
Bug reference: 5242
Logged by: Gerhard Lutz
Email address: gerhard.l...@mbtech-group.com
PostgreSQL version: 8.4.1
Operating system: Windows XP
On Tue, Dec 15, 2009 at 1:23 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
If we're to do anything about this, it is spilling the trigger queue so
it doesn't eat an unbounded amount of memory.
Of course, the reason nothing much has been done about
On Tue, Dec 15, 2009 at 1:33 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Dec 15, 2009 at 1:23 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
If we're to do anything about this, it is spilling the trigger
On Tue, Dec 15, 2009 at 2:42 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
This bug report form can be used for reporting bugs and problems with
the PostgreSQL database, for problems with database connectors such as
ODBC and JDBC, graphical administration tools such as pgAdmin or other
On Tue, Dec 15, 2009 at 3:45 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Err, sorry, I quoted the wrong part. I meant, how would you rlimit
the server memory usage?
Put a ulimit command in the server start script? Depending on the
details of the start
On Mon, Dec 14, 2009 at 12:32 PM, Greg Sabino Mullane g...@turnstep.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
The new explain formats break if you have a multi-query statement.
I don't have time to fix at the moment, but I'll try and explain
the problem. For YAML, the
On Mon, Dec 14, 2009 at 12:59 PM, Robert Haas robertmh...@gmail.com wrote:
The new explain formats break if you have a multi-query statement.
I will fix this, unless someone else beats me to it.
Proposed patch attached. The problem with JSON output is pretty
simple - ExplainSeparatePlans
Woops, forgot to copy the list.
On Sat, Dec 12, 2009 at 2:15 PM, Robert Haas robertmh...@gmail.com wrote:
On Sat, Dec 12, 2009 at 2:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Roman Kononov kono...@ftml.net writes:
The bitfromint8() and bitfromint4() are hosed. They produce wrong
results when
On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I'm not an expert on this area of the code, but can we just ignore
isNatural and usingClause when deparsing?
No. These properties are *not* ignorable because doing so changes
On Thu, Dec 10, 2009 at 10:48 AM, Andrew Gierth
and...@tao11.riddles.org.uk wrote:
Robert == Robert Haas robertmh...@gmail.com writes:
On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
My reading of the spec is that USING (and therefore NATURAL) is
defined to join
On Thu, Dec 10, 2009 at 11:57 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andrew Gierth and...@tao11.riddles.org.uk writes:
There's another possible solution (albeit a somewhat nontrivial one)
which came up when a bunch of us were talking about this one on IRC;
which is to handle the problem in the
On Thu, Dec 10, 2009 at 11:54 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
My reading of the spec is that USING (and therefore NATURAL) is defined
to join identically named columns
On Thu, Dec 10, 2009 at 1:02 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Robert Haas escribió:
On Thu, Dec 10, 2009 at 11:57 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Hmm. Cute, but I wonder why we shouldn't just be throwing an error.
As I said last night, the only thing I see wrong
On Thu, Dec 10, 2009 at 12:32 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Dec 10, 2009 at 11:54 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The problem with USING is that it is not merely a join condition but
affects the set of columns emitted
On Tue, Dec 8, 2009 at 11:08 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee:
You are right, it crushes on following statement: select
instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual
2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee:
This the end of core dump. It is 8.3M bzip-ed. I can provide it on the
request.
I think maybe the beginning would be more useful than the end.
...Robert
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee:
Once more:
http://www.fts.ee/pgsqldebug.tgz - with loging enabled
http://www.ftse.ee/pg_core.tar.bzip2 - full core dump
It looks like you've got a pl/pgsql function that called itself
recursively 1417 times before running out of stack space.
2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee:
You are right, it crushes on following statement: select
instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual;
max_stack_depth is commented out, I think it has the default value:
#max_stack_depth = 2MB
Well, my guess is you have
On Fri, Dec 4, 2009 at 12:24 AM, maithili manur
maithili.manur...@gmail.com wrote:
Please find attached the screenshots. The first two are screenshots of the
installtions process and the last one is where it fails.
The environment is such :
The machine on which postgres 8.2 is being installed
On Thu, Dec 3, 2009 at 7:07 AM, aftab akha...@hotmail.co.uk wrote:
The following bug has been logged online:
Bug reference: 5230
Logged by: aftab
Email address: akha...@hotmail.co.uk
PostgreSQL version: 8.3.8
Operating system: Centos 5
Description: Limit
501 - 600 of 731 matches
Mail list logo
