On Mon, Jan 11, 2010 at 2:00 AM, Michael Tenenbaum
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5271
> Logged by: Michael Tenenbaum
> Email address: mich...@strategic-techs.com
> PostgreSQL version: 8.3.9
> Operating system: Gentoo Linux
> Descriptio
On Sun, Jan 10, 2010 at 10:22 AM, Kevin Grittner
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 perhaps
confusing the cl
On Thu, Jan 7, 2010 at 7:31 PM, Mark Kirkwood
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 source? Maybe I can
On Tue, Oct 6, 2009 at 8:38 PM, Matthew Byrne wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5098
> Logged by: Matthew Byrne
> Email address: matt...@hairybrain.co.uk
> PostgreSQL version: 8.4.1
> Operating system: Linux x86_64 (Ubuntu 9.04)
> Descript
On Thu, Jan 7, 2010 at 11:39 AM, Tom Lane wrote:
> Robert Haas 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 just do getcw
On Thu, Jan 7, 2010 at 7:51 AM, Mike Landis 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 unspecified include
On Thu, Jan 7, 2010 at 10:00 AM, Michael Felt 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 only
applies to W
On Thu, Jan 7, 2010 at 9:16 AM, Alvaro Herrera
wrote:
> Robert Haas escribió:
>> On Wed, Jan 6, 2010 at 11:13 PM, Mike Landis wrote:
>> > Can you please stop displaying the email addresses on bug reports? It's
>> > one
>> > thing to require an email
On Wed, Jan 6, 2010 at 11:13 PM, Mike Landis 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...
> http://archives.po
On Mon, Jan 4, 2010 at 8:44 AM, Takesver Kumar Thakur
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
> Operating system: cent
On Sun, Jan 3, 2010 at 10:48 PM, Ben Woosley 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 "alter table ad
On Mon, Jan 4, 2010 at 5:29 AM, Toni Helenius
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 2008 Server Enterprise
>
2010/1/2 Tomas Studva :
> 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 -
> http://www.mail-archive.com/pgsql-bugs@postgresql.org/msg24810.html
>
On Wed, Dec 30, 2009 at 7:36 AM, Gaurav K Srivastav 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 database serv
On Mon, Dec 21, 2009 at 7:05 AM, Ashish Anand 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 EnterpriseDB.
>
>
On Thu, Dec 17, 2009 at 4:06 PM, Ashish Anand 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
> Description: Tutori
On Wed, Dec 16, 2009 at 1:14 PM, David Lerner
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 XPpro SP3
> Description:
On Wed, Dec 16, 2009 at 9:03 PM, Craig Ringer
wrote:
> On 16/12/2009 11:55 PM, Robert Haas wrote:
>>
>> On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagander
>> wrote:
>>>
>>> On Wed, Dec 16, 2009 at 16:12, Tom Lane wrote:
>>>>
>>&
On Mon, Dec 14, 2009 at 10:06 PM, Robert Haas wrote:
> On Mon, Dec 14, 2009 at 12:59 PM, Robert Haas 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. [...di
On Wed, Dec 16, 2009 at 11:05 AM, Alvaro Herrera
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 lea
On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagander wrote:
> On Wed, Dec 16, 2009 at 16:12, Tom Lane wrote:
>> Alvaro Herrera writes:
>>> Alexey Luchko wrote:
postgres.exe!mdpostckpt+0x181b38
postgres.exe!mdpostckpt+0x18bbdb
>>
>>> This stack trace seems bogus. The stats collector shoul
On Tue, Dec 15, 2009 at 11:18 PM, Philip Graham wrote:
> Robert Haas wrote:
>>
>> On Mon, Dec 14, 2009 at 11:15 PM, Philip Graham
>> wrote:
>>
>>>
>>> The following bug has been logged online:
>>>
>>> Bug reference: 5244
&g
On Wed, Dec 16, 2009 at 4:35 AM, Stefan Kaltenbrunner
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:
http://www.postgresql.org/mailp
On Tue, Dec 15, 2009 at 3:45 PM, Tom Lane wrote:
> Robert Haas 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 script
On Tue, Dec 15, 2009 at 2:42 PM, Alvaro Herrera
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
> external projects do n
On Tue, Dec 15, 2009 at 1:33 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, Dec 15, 2009 at 1:23 PM, Tom Lane wrote:
>>> Alvaro Herrera writes:
>>>> If we're to do anything about this, it is spilling the trigger queue so
>>>> it doesn&
On Tue, Dec 15, 2009 at 12:22 PM, Magnus Hagander wrote:
>> And to the list: can we PLEASE, PRETTY PLEASE add a note about this on
>> the bug submission page? I asked for this before and Tom concurred,
>> but I'm not aware that anything has been done about it. What do I
>> have to do to make thi
On Tue, Dec 15, 2009 at 1:23 PM, Tom Lane wrote:
> Alvaro Herrera 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 that is that
> by the time your trigger
On Mon, Dec 14, 2009 at 2:57 AM, Gerhard Lutz
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
> Description:
On Tue, Dec 15, 2009 at 12:07 PM, Greg Stark wrote:
> On Tue, Dec 15, 2009 at 4:16 PM, Robert Haas 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
On Mon, Dec 14, 2009 at 11:15 PM, Philip Graham 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: Attempting t
On Tue, Dec 15, 2009 at 11:02 AM, Greg Stark wrote:
> On Tue, Dec 15, 2009 at 3:44 PM, Robert Haas 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 of a
>>
On Tue, Dec 15, 2009 at 12:09 AM, Craig Ringer
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 means your server is m
On Mon, Dec 14, 2009 at 12:59 PM, Robert Haas 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() still th
On Mon, Dec 14, 2009 at 12:32 PM, Greg Sabino Mullane 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 forced lead
Woops, forgot to copy the list.
On Sat, Dec 12, 2009 at 2:15 PM, Robert Haas wrote:
> On Sat, Dec 12, 2009 at 2:00 PM, Tom Lane wrote:
>> Roman Kononov writes:
>>> The bitfromint8() and bitfromint4() are hosed. They produce wrong
>>> results when the BIT
On Thu, Dec 10, 2009 at 12:32 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Dec 10, 2009 at 11:54 AM, Tom Lane wrote:
>>> The problem with USING is that it is not merely a join condition but
>>> affects the set of columns emitted by the join. It can't
On Thu, Dec 10, 2009 at 1:02 PM, Alvaro Herrera
wrote:
> Robert Haas escribió:
>> On Thu, Dec 10, 2009 at 11:57 AM, Tom Lane 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 wron
On Thu, Dec 10, 2009 at 11:54 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane wrote:
>>> My reading of the spec is that USING (and therefore NATURAL) is defined
>>> to join identically named columns. Therefore, renaming one of t
On Thu, Dec 10, 2009 at 11:57 AM, Tom Lane wrote:
> Andrew Gierth 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 view deparse: if a column used
>> in a
On Thu, Dec 10, 2009 at 10:48 AM, Andrew Gierth
wrote:
>>>>>> "Robert" == Robert Haas writes:
>
> > On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane wrote:
> >>
> >> My reading of the spec is that USING (and therefore NATURAL) is
> >>
On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane wrote:
> Robert Haas 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 the
> se
On Sun, Dec 6, 2009 at 5:41 PM, Sergey Burladyan wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5234
> Logged by: Sergey Burladyan
> Email address: eshkin...@gmail.com
> PostgreSQL version: 8.3.8
> Operating system: Debian GNU/Linux 5.0.3 (lenny) + tes
On Tue, Dec 8, 2009 at 11:08 PM, Tom Lane wrote:
> Robert Haas writes:
>> 2009/12/8 Oleg Jurtšenko :
>>> You are right, it crushes on following statement: "select
>>> instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual;"
>
2009/12/8 Oleg Jurtšenko :
> 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 your kernel limit
2009/12/8 Oleg Jurtšenko :
> 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. What do you
have max
2009/12/8 Oleg Jurtšenko :
> Both files are there.
Both files are where? I don't see an attachment or a link.
...Robert
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
2009/12/8 Oleg Jurtšenko :
> 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 subscription:
http://ww
On Fri, Dec 4, 2009 at 12:24 AM, maithili manur
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 is Win 2K3 Japanese OS
On Fri, Nov 27, 2009 at 8:09 AM, Martin wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5217
> Logged by: Martin
> Email address: searepo...@aol.at
> PostgreSQL version: 8.4.1
> Operating system: M$ Vista (but does not matter) same on XP, ...
> Descript
On Thu, Dec 3, 2009 at 8:21 PM, Fred Wei wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5233
> Logged by: Fred Wei
> Email address: w...@niwa.co.nz
> PostgreSQL version: 8.1.11
> Operating system: SUSE Linux Enterprise Server 10 SP2 (x86_64)
> Descript
On Thu, Dec 3, 2009 at 10:45 AM, aftab khan wrote:
> This is not exactly the same what I posted yesterday, What I have posted
> today also include EXPLAIN ANALYZE OUTPUT .
[ adding the list back to the CC line ]
It looks like you have a problem very similar to one Laurence Laborde
was complainin
On Thu, Dec 3, 2009 at 7:07 AM, aftab 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 operator slows down
On Thu, Nov 26, 2009 at 5:41 AM, Walter Willmertinger wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5215
> Logged by: Walter Willmertinger
> Email address: will...@gmail.com
> PostgreSQL version: 8.4.1
> Operating system: Windows XP Prof.
> Descriptio
On Wed, Dec 2, 2009 at 11:42 AM, Craig Ringer
wrote:
> On 2/12/2009 10:35 PM, aftab wrote:
>>
>> The following bug has been logged online:
>>
>> Bug reference: 5226
>> Logged by: aftab
>> Email address: akha...@hotmail.co.uk
>> PostgreSQL version: 8.3.8
>> Operating system: Ce
On Mon, Nov 30, 2009 at 1:42 PM, Pavel Stehule wrote:
> 2009/11/30 Tom Lane :
>> Pavel Stehule writes:
>>> I thing so ex-MySQL needs exact DESCRIBE, exact SHOW statement. It is
>>> some, what they used long time and then they missing it.
>>
>> You know, if they're not willing to make any adaptati
On Mon, Nov 30, 2009 at 12:28 PM, Pavel Stehule wrote:
>>
>> Rather than trying to be compatible with MySQL directly, I think we
>> might be better off adding a chapter to our documentation explaining
>> to ex-MySQL users how to accomplish the same things in PostgreSQL. We
>> might even think abo
On Sat, Nov 28, 2009 at 5:34 PM, Russell Wallace
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5218
> Logged by: Russell Wallace
> Email address: russell.wall...@gmail.com
> PostgreSQL version: 8.4.1
> Operating system: Windows
> Description: E
On Fri, Nov 27, 2009 at 3:42 AM, Denny Saviant Mohammad
wrote:
> Well, i changed nothing in my postgresql.conf before the accident.
Well, someone or something did, because stdmsg isn't ever a legal
value, and it didn't put itself into that file.
.
> But, after i try changing value on log_destinat
On Fri, Nov 27, 2009 at 1:42 AM, Peter Eisentraut wrote:
> On tor, 2009-11-26 at 22:59 -0500, Robert Haas wrote:
>> ISTM that if you run psql with "-f -", you shouldn't expect to get an
>> interactive shell. Rather, you should expect psql to do whatever it
On Thu, Oct 22, 2009 at 2:42 PM, Stephen Frost wrote:
> -1 appears to be ignored when '-f -' is set.
I've been bitten by this, too. It appears that "-f -" is in general
equivalent to not specifying "-f" at all. In startup.c we have a test
for:
options.action == ACT_FILE && strcmp(options.acti
On Mon, Nov 23, 2009 at 4:21 AM, Maithili wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5210
> Logged by: Maithili
> Email address: maithili.manur...@gmail.com
> PostgreSQL version: 8.2
> Operating system: Windows 2003
> Description: error in i
On Tue, Nov 24, 2009 at 6:04 AM, lee brown wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5211
> Logged by: lee brown
> Email address: lee_bro...@msn.com
> PostgreSQL version: 8.3
> Operating system: vista
> Description: invalid password
> Detai
On Sat, Nov 21, 2009 at 9:13 AM, denny saviant
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5207
> Logged by: denny saviant
> Email address: konohabluefl...@gmail.com
> PostgreSQL version: 8.4.1
> Operating system: windows xp pro sp3
> Description:
On Fri, Nov 20, 2009 at 6:56 PM, Alvaro Herrera wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5206
> Logged by: Alvaro Herrera
> Email address: alvhe...@postgresql.org
> PostgreSQL version: any
> Operating system: any
> Description: wal_sync_me
On Fri, Nov 20, 2009 at 6:44 PM, Alain Baeckeroot
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5205
> Logged by: Alain Baeckeroot
> Email address: alain.baecker...@laposte.net
> PostgreSQL version: 8.4.1
> Operating system: Linux (Ubuntu 9.10)
> Desc
On Fri, Nov 20, 2009 at 9:58 AM, Marcel Wieland
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5202
> Logged by: Marcel Wieland
> Email address: marcel.wiel...@fondsnet.de
> PostgreSQL version: 8.2
> Operating system: Linux
> Description: Rule a
On Fri, Nov 20, 2009 at 10:11 AM, Marcel Wieland
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5203
> Logged by: Marcel Wieland
> Email address: marcel.wiel...@fondsnet.de
> PostgreSQL version: 8.2
> Operating system: Linux
> Description: Rule
On Wed, Nov 18, 2009 at 11:26 PM, Joseph Shraibman wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5197
> Logged by: Joseph Shraibman
> Email address: ...@selectacast.net
> PostgreSQL version: 8.2.14
> Operating system: Linux
> Description: JDBC:
I see that there's been no response to bugs #5194, #5187, #5051.
Should we consider adding a message to the bug reporting page that
suggests emailing the relevant list directly for JDBC/ODBC bugs? We
seem to get a lot of those here. The other frequent one that seems to
come up is the one-click in
On Mon, Nov 9, 2009 at 7:21 PM, Vijaya Krishna Cherukuri
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5175
> Logged by: Vijaya Krishna Cherukuri
> Email address: krisveejay...@gmail.com
> PostgreSQL version: 8.3.8
> Operating system: Debian Linux
> D
On Mon, Nov 16, 2009 at 12:59 PM, Clark Pearson
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5191
> Logged by: Clark Pearson
> Email address: cloink_frigg...@ntlworld.com
> PostgreSQL version: 8.3.7
> Operating system: Windows
> Description: n
On Fri, Nov 13, 2009 at 8:52 PM, obelich wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5186
> Logged by: obelich
> Email address: obel...@gmail.com
> PostgreSQL version: 8.4.1
> Operating system: Opensuse 11.2
> Description: Not install daemon
On Fri, Nov 13, 2009 at 10:39 AM, Heikki Linnakangas
wrote:
> Tom Lane wrote:
>> Robert Haas writes:
>>> I think it would be over the top to suggest that pg_dump has to cope
>>> with modifications that can only occur through manual updates to the
>>> system
On Fri, Nov 13, 2009 at 1:13 AM, Tom Lane wrote:
> "Robert Haas" writes:
>> The following command does not change the output of "pg_dumpall":
>> alter tablespace pg_default owner to bob;
>
> I don't think this is a bug. It's one specific aspect
The following bug has been logged online:
Bug reference: 5184
Logged by: Robert Haas
Email address: robertmh...@gmail.com
PostgreSQL version: CVS HEAD
Operating system: Linux
Description:default tablespace owner is not dumped
Details:
The following command does not
On Tue, Oct 20, 2009 at 12:19 PM, wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5128
> Logged by:
> Email address: landrevi...@deadtreepages.com
> PostgreSQL version: 8.4
> Operating system: FreeBSD
> Description: Returning nested composite types in pl
On Sat, Nov 7, 2009 at 5:23 AM, Peter Eisentraut wrote:
> On fre, 2009-11-06 at 17:29 +, Jason wrote:
>> When I have a plpythonu function returning a composite type that has an
>> array column, the function does not work when I try to return a list for
>> that column.
>
> There is a patch prop
On Tue, Nov 3, 2009 at 10:04 AM, christian david
wrote:
>
> 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:
On Wed, Nov 4, 2009 at 3:35 PM, Tom Lane wrote:
> "assaf" writes:
>> PostgreSQL version: 8.37
>> Description: Poor performance with Left-join where right side does
>> not exist
>
> 8.4 might be smarter about this case for you. It's hard to tell for sure
> with so few details.
EXPLAIN out
2009/11/2 donniehan :
> Hi Tom,
>
> I agree with Hxli. It may be a good way to add permissions check when create
> the view.
>
> I also find 2 pieces of words in the document about the owner of the object.
>
> "By default, only the owner of an object can do anything with the object."
>
> "as th
On Tue, Oct 27, 2009 at 10:47 AM, Marcus Lundblad
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5140
> Logged by: Marcus Lundblad
> Email address: marcus.lundb...@mogul.com
> PostgreSQL version: 8.3.8
> Operating system: Solaris 10
> Description:
On Fri, Oct 30, 2009 at 11:51 PM, John R Pierce wrote:
> Tom Lane wrote:
>>
>> There is special-purpose software out there that can compute exactly
>> with rational numbers, but you aren't likely to find it embedded in any
>> general-purpose tools like databases --- the use-case just isn't wide
>>
On Fri, Oct 30, 2009 at 1:39 AM, Gray wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5150
> Logged by: Gray
> Email address: g...@ms-irk.ru
> PostgreSQL version: 8.2.6
> Operating system: i686-pc-linux-gnu
> Description: math bug
> Details:
>
>
On Thu, Oct 29, 2009 at 6:14 PM, Don Fox wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5149
> Logged by: Don Fox
> Email address: donf...@mac.com
> PostgreSQL version: 8.4.1
> Operating system: Mac X Snowleopard
> Description: Can't untar the s
On Thu, Oct 22, 2009 at 10:47 AM, flamin dragon wrote:
>
>
> 2009/10/22 Robert Haas
>>
>> On Wed, Oct 21, 2009 at 12:51 PM, wrote:
>> >
>> > The following bug has been logged online:
>> >
>> > Bug reference: 5130
>>
On Sat, Sep 5, 2009 at 5:42 AM, Kamil Roman wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5039
> Logged by: Kamil Roman
> Email address: kamil.lech.ro...@gmail.com
> PostgreSQL version: 8.3.7
> Operating system: Windows XP
> Description: 'i' fl
On Fri, Aug 28, 2009 at 9:59 AM, Dan O'Hara wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5021
> Logged by: Dan O'Hara
> Email address: danarasoftw...@gmail.com
> PostgreSQL version: 8.3.7
> Operating system: win32
> Description: ts_parse doesn
2009/9/29 Yaming Gu :
> Hi, Robert,
>
> According to your recommendations, I tried to load plperu, almost the same
> error messages have shown:
>
> D:\Program Files\Postgresql\8.3\bin>createlang -U postgres plperlu example
>
> Password:
>
> createlang: language installation failed: server closed t
On Thu, Oct 22, 2009 at 3:23 AM, Geok Hua Yap wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5132
> Logged by: Geok Hua Yap
> Email address: geokhua8...@yahoo.com.sg
> PostgreSQL version: 8.3.1
> Operating system: CentOS 5.2
> Description: Inval
On Wed, Oct 21, 2009 at 12:51 PM, wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5130
> Logged by:
> Email address: flamindrag...@gmail.com
> PostgreSQL version: any
> Operating system: Win XP Pro SP2
> Description: Failed to run initdb:1
> Details:
>
>
On Wed, Oct 21, 2009 at 11:23 PM, aihongwei wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5131
> Logged by: aihongwei
> Email address: ufo008...@163.com
> PostgreSQL version: 8.0.0
> Operating system: linux x86_64
> Description: The pgsql will
On Tue, Oct 6, 2009 at 9:38 PM, Matthew Byrne wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5098
> Logged by: Matthew Byrne
> Email address: matt...@hairybrain.co.uk
> PostgreSQL version: 8.4.1
> Operating system: Linux x86_64 (Ubuntu 9.04)
> Descript
On Wed, Oct 14, 2009 at 9:56 AM, wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5114
> Logged by:
> Email address: flamindrag...@gmail.com
> PostgreSQL version: any
> Operating system: Win XP Pro SP2
> Description: database initialization
> Details:
>
>
2009/10/16 malu :
>
> The following bug has been logged online:
>
> Bug reference: 5124
> Logged by: malu
> Email address: maluulam_l...@yahoo.com.mx
> PostgreSQL version: 8.3
> Operating system: windows xp proffeional
> Description: visualizacion de registros
> Details:
On Fri, Oct 16, 2009 at 2:04 PM, Kevin Grittner
wrote:
> Robert Haas wrote:
>
>> UUIDs throw away 6 bits?
>
> http://en.wikipedia.org/wiki/Universally_Unique_Identifier#Version_4_.28random.29
How about that. You learn something new every day.
...Robert
--
Sent via pgsql
On Fri, Oct 16, 2009 at 11:08 AM, Kevin Grittner
wrote:
> Robert Haas wrote:
>
>> Well, then Tom's idea of using a random number seems pretty solid no
>> matter how you slice it. Maybe a UUID.
>
> A random number is looking like the best option. I'm not
On Fri, Oct 16, 2009 at 10:33 AM, Kevin Grittner
wrote:
> Pedro Gimeno wrote:
>> Tom Lane wrote:
>>
>>> This could be addressed by having the postmaster report its $PGDATA
>>> value in the pg_ping response, but I would be against that on
>>> security grounds. We don't let nonprivileged users kno
On Fri, Oct 16, 2009 at 6:39 AM, Heikki Linnakangas
wrote:
> Thom Brown wrote:
>> This is either a bug in vacuumdb with it not using the correct order,
>> or postgres shouldn't be paying attention to the order of the
>> keywords. In any case, it doesn't work. I've searched the postgres
>> FAQs,
On Sun, Sep 27, 2009 at 5:29 PM, Jesper wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5083
> Logged by: Jesper
> Email address: sol...@hotmail.com
> PostgreSQL version: 8,3
> Operating system: Vista
> Description: Problem create account.
> Deta
601 - 700 of 787 matches
Mail list logo
