On 08/02/2013 01:04 PM, Bruce Momjian wrote:
On Wed, Jul 10, 2013 at 07:07:54PM +, jaroslav.pota...@gmail.com wrote:
The following bug has been logged on the website:
Bug reference: 8293
Logged by: Yaroslav Potapov
Email address: jaroslav.pota...@gmail.com
PostgreSQL ver
On 07/25/2013 09:48 AM, Tom Lane wrote:
Andres Freund writes:
Before that commit the checks for cmsgcred which includes sys/ucred.h
happened to include params.h... Patch attached, missing the configure
update since I don't have a compatible autoconf on my laptop, to produce
a minimal diff.
Co
On 07/01/2013 05:35 PM, Peter Eisentraut wrote:
On 7/1/13 9:19 AM, Tom Lane wrote:
AFAICT, the result in this case would be that the script comes to the
wrong conclusion about whether ucred.h is available. Wouldn't that
result in a build failure, or at least missing features? IOW, don't
we ne
On 06/30/2013 11:07 AM, Andres Freund wrote:
On 2013-06-30 10:17:50 -0400, Andrew Dunstan wrote:
On 06/30/2013 09:49 AM, Tom Lane wrote:
Andrew Dunstan writes:
On 2013-06-30 15:17:20 +0200, Andres Freund wrote:
Andrew: Could we perhaps check for the "Report this to" bit in the
On 06/30/2013 09:49 AM, Tom Lane wrote:
Andrew Dunstan writes:
On 2013-06-30 15:17:20 +0200, Andres Freund wrote:
Andrew: Could we perhaps check for the "Report this to" bit in the
buildfarm?
I'm not sure what you're asking here.
I think he's wishing that if config
On 06/30/2013 09:20 AM, Andres Freund wrote:
On 2013-06-30 15:17:20 +0200, Andres Freund wrote:
Andrew: Could we perhaps check for the "Report this to" bit in the
buildfarm?
FWIW: I checked that there are no other reports on HEAD atm.
I'm not sure what you're asking here. Where exactly do
On 11/13/2012 12:17 PM, Tom Lane wrote:
pgm...@joh.to writes:
I have a reproducible segmentation fault in PL/Perl. I have yet to narrow
down the test case to something sensible, but I do have a backtrace:
219 while (context->firstchild != NULL)
(gdb) bt
#0 0x000104e90782 in Me
On 05/21/2012 02:59 PM, Andrew Dunstan wrote:
On 05/16/2012 10:23 AM, Andrew Dunstan wrote:
On Wed, May 16, 2012 at 9:08 AM, Tom Lane <mailto:t...@sss.pgh.pa.us>> wrote:
Martin Pitt mailto:mp...@debian.org>> writes:
> while packaging 9.2 beta 1 for Debian/Ubu
On 05/16/2012 10:23 AM, Andrew Dunstan wrote:
On Wed, May 16, 2012 at 9:08 AM, Tom Lane <mailto:t...@sss.pgh.pa.us>> wrote:
Martin Pitt mailto:mp...@debian.org>> writes:
> while packaging 9.2 beta 1 for Debian/Ubuntu the postgresql-common
> test suite not
On Wed, May 16, 2012 at 9:08 AM, Tom Lane wrote:
> Martin Pitt writes:
> > while packaging 9.2 beta 1 for Debian/Ubuntu the postgresql-common
> > test suite noticed a regression: It seems that pg_restore --data-only
> > now skips the current value of sequences, so that in the upgraded
> > databa
On 07/05/2011 11:23 AM, Robert Haas wrote:
Yeah. In particular, it conflicts with the ancient copy syntax which
we still support for backwards compatibility with versions< 7.3. We
can fix the immediate problem with something like the attached.
(a) Should we do that?
yes.
(b) Should we
Tom Lane wrote:
Anyway, you'll get the same "not safe" bleat for any message
logged during early postmaster startup.
Maybe we should just drop the "not safe" message. It's not conveying
anything very helpful, I think. The useful bit of the behavior is to
shove the original message out to std
Robert Haas wrote:
On Mon, Jun 7, 2010 at 10:37 AM, Greg Sabino Mullane wrote:
Tom Lane wrote:
I don't think the above would be particularly hard to implement myself,
but if it becomes a really big deal, we can certainly punt by simply
quoting anything containing an indicator (the special
Magnus Hagander wrote:
From a quick look, it looks fine to me. I don't have time to do a
complete check right now, but I'll do that as soon as I can and then
commit it - unless people feel it's more urgent than maybe a week
worst case, in which case someone else has to pick it up :-)
I'd
Dave Page wrote:
On Fri, Oct 16, 2009 at 7:03 PM, Jesse Morris wrote:
-Original Message-
From: Dave Page [mailto:dp...@pgadmin.org]
Sent: Friday, October 16, 2009 2:14 AM
To: Jesse Morris
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Re: BUG #5065: pg_ctl start fails as
Simon Riggs wrote:
On Fri, 2009-05-15 at 10:17 -0400, Andrew Dunstan wrote:
This whole area is unfortunately way too fragile. We need some way of
managing these facilities that hides a lot of these details and is
therefore less likely to produce shot feet, IMNSHO. I get very nervous
Simon Riggs wrote:
On Fri, 2009-05-15 at 22:56 +0900, Fujii Masao wrote:
OK, I probably understood your point. The timeline history files whose
timeline ID is larger than that of an oldest backup must not be deleted
from the archive. On the other hand, the smaller or equal one can be
delet
Alex Hunsaker wrote:
On Tue, Nov 4, 2008 at 15:02, Alex Hunsaker <[EMAIL PROTECTED]> wrote:
On Tue, Nov 4, 2008 at 14:43, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
But by all means if you can come up with a robust way of allowing
the more traditional way of calling s
Alex Hunsaker wrote:
On Tue, Nov 4, 2008 at 12:43, Alex Hunsaker <[EMAIL PROTECTED]> wrote:
It has something to do with anon subs not sure what...
It has to do with us returning the anonymous sub inside of the safe
and then calling the function outside of the safe (or at least in a
d
Tom Lane wrote:
The point being that the config files are opened with AllocateFile(),
which in turn calls fopen(). It doesn't use open(). The proposal was
only to make all *open()* calls do it binary. I was under the impression
that on Unix, that's what open() did, so we should behave the same?
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Well, why is that a bug? If the platform is so silly as to define text
files that way, who are we to argue?
The problem is that our pg_controldata might have binary values that
contain 0x1a that wi
Magnus Hagander wrote:
I had a chat with Heikki about this, and the proper way to fix it.
Should there actually be any reason not to *always* open our files with
O_BINARY? That seems to be what should mimic what Unix does, which would
be what we expect, no?
If that is so, then I propose we do
Magnus Hagander wrote:
I have a patch working for me, I've sent it over to Gevik for testing in
his environment. Attached here if somebody else wants to play.
Looks OK.
cheers
andrew
---(end of broadcast)---
TIP 4: Have you searched our
Magnus Hagander wrote:
On Wed, Feb 06, 2008 at 02:59:31PM +0100, Gevik Babakhani wrote:
I might be very wrong, but when I try to install 8.3 on Windows with NLS
options selected, no share/locale files are installed. could someone please
test or confirm this?
Yes, it's broken. It seem
Alvaro Herrera wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
not sure I want to add si
Alvaro Herrera wrote:
Andrew Dunstan wrote:
OK, works for me. I'll try to look at it after I have attended to the
Windows build issues. My plate is pretty full right now, though.
FYI I'm having a look at it now.
Great. Thanks.
cheers
andrew
-
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
One issue here is that CONTEXT is potentially multiple lines. I'm not
sure that there is much we can do about that, especially not at the last
minute. If we had some time to rewrite internal APIs
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
not sure I want to add six more text fields to the CSV fo
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
I can't see any very good reason for text logs to have different
content from CSV logs.
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text fie
Tom Lane wrote:
"depesz" <[EMAIL PROTECTED]> writes:
Description:csvlog skips some logs
The point here is that CSV-format log output doesn't include the
DETAIL, HINT, or context (QUERY/STATEMENT/CONTEXT) lines that
you might get with normal output.
I suppose this was intenti
Tom Lane wrote:
"Matt" <[EMAIL PROTECTED]> writes:
Description:plperl spi_exec_prepared variable undef value confusion
[ pokes at it ... ] Some of the places in plperl.c that are checking for
undef values use code like
if (SvOK(val) && SvTYPE(val) != SVt_NULL)
and
Magnus Hagander wrote:
The effective max count on Unixen is typically in the thousands,
and I'd suggest the same on Windows unless there's some efficiency
reason to keep it small (in which case, maybe ten would do).
AFAIK there's no problem with huge numbers (it takes an int32, and the
do
Tom Lane wrote:
> This is closely related to the discussion a couple weeks ago about how
> a LEFT JOIN could produce nulls in an output column that was labeled as
> having a non-null-domain type. We haven't figured out what is a sane
> behavior for that case, either. I'm beginning to think that
Tom Lane wrote:
> I wrote:
>> It looks to me like basically everywhere in plperl.c that does newSVpv()
>> should follow it with
>>
>> #if PERL_BCDVERSION >= 0x5006000L
>> if (GetDatabaseEncoding() == PG_UTF8)
>> SvUTF8_on(sv);
>> #endif
>
> Experimentation proved that th
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
David Fetter wrote:
+ /* Disallow BADCHARS characters */
+ if (strcspn(cstate->delim, BADCHARS) != 1)
+ ereport(ERROR,
+ (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
+errmsg("COPY delimiter cannot be \"%#02x\"",
+
Steve McWilliams wrote:
Nevermind, I found out what this was. Turned out that the customer
machine in question had particularly heavy security settings and so the
enetaware account did not have permission to write into the directory
where it was trying to create PGDATA. Once I widened the settin
Matthew T. O'Connor wrote:
Tom Lane wrote:
If someone can whip up and test a WIN32 version of this, I'll take care
of the rest.
I can't do the coding, but I took a quick look at msdn and I think
this is relevant:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platfo
Bruce Momjian wrote:
[EMAIL PROTECTED] wrote:
Hi Folks,
I installed postgresql8.0b1 a fews days back.
I am listing the issues which i came across
these many be already known issues or may not
be bugs.
1. Automatic convertion to NTFS.
Many NT based windows installation may not
have formatted the
39 matches
Mail list logo
