not directly
issued by the client here.
If this is the behavior we want for SQL functions, that is something
that ought to be highlighted as a special case.
--
Peter Geoghegan
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
006ffca9 in BackendStartup (port=0x239e2b0) at postmaster.c:3304
#68 0x006fcacb in ServerLoop () at postmaster.c:1367
#69 0x006fc3c2 in PostmasterMain (argc=2, argv=0x23792a0) at
postmaster.c:1127
#70 0x006676ba in main (argc=2, argv=0x23792a0) at main.c:199
These pg_stat_st
On Tue, May 14, 2013 at 2:47 PM, John R Pierce wrote:
> on a typical unix system, with one user connection active, I see 8 processes
> active at present...
To be fair, you need to use process explorer or something to see
equivalent information on Windows. Most people never will.
--
On 30 March 2013 14:01, wrote:
> env CFLAGS='-O3 -march=native' ./configure --with-segsize=128
Why did you build with a segment size of 128GB? Postgres binaries
built with a non-standard segment size are not widely used.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-bugs
ink you're safe.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
rd-party library that does maintain such a database so
> that this module could be based upon that instead of having to maintain
> the database itself?
No, there is not.
The textual representation of the types - the dashes - are fairly odd,
but it's too late to fix that.
--
Regard
is correct using SQL, using this simple method:
https://en.wikipedia.org/wiki/EAN-13#Calculation_of_checksum_digit
We actually discussed changing the formatting of isn along the lines
you've discussed, and it was shot down. I'd just like to see it go.
--
Regards,
Peter Geoghegan
--
Sent via pgs
ur may be astonishing, but that
doesn't make it a POLA violation. I don't have time to check now, but
I'm pretty sure that doing something else would break a whole bunch of
other common cases.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Suppor
x-like
systems follow LLP64 (or LLP32) in practice. sizeof(int) is 4 on
Windows (though, in contrast to LLP64, sizeof(long) is 4 too on 64-bit
windows).
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailin
will work rather than fail.
Right. sizeof(int) is very probably 4 on all platforms that we
support. I see no problem with the proposal.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-b
seems to think can cause this error
with poll(), so this seems like a slight variant of the problem
reported by Sean Chittenden (kernel resource exhaustion causes pipe
creation to fail, with unnecessarily bad consequences for Postgres).
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL
dtyje6wtuy4tgdjuq6eutjjp0ctfladp9qwp8got...@mail.gmail.com
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
q version that actually has commit
4e816286533dd34c10b368487d4079595a3e1418, can you produce a GDB back
trace of the php process, by doing the same thing as the complainant
that posted to the php bug tracker? The process is documented here:
https://bugs.php.net/bugs-generating-backtrace.php
--
Pe
; /lib64/libdl.so.2 (0x7f87530a4000)
libutil.so.1 => /lib64/libutil.so.1 (0x7f8752ea1000)
libm.so.6 => /lib64/libm.so.6 (0x7f8752ba6000)
/lib64/ld-linux-x86-64.so.2 (0x003cdc40)
Is the libpq shared object you see here (but for pgsql.so) the one
tha
de may have contained errors, even though it was
evident to me that they actually did not. That said, it probably
wouldn't hurt to give it another try sometime soon.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sen
On 29 January 2012 23:47, Josh Berkus wrote:
> This is *so* not a discussion to have on the pgsql-bugs list. Please
> take it to -hackers.
I suppose you're right, since the first discussion occurred there and
didn't really go anywhere.
--
Peter Geoghegan http://www
line with this
stuff. Should I continue to report trivialities like these as bugs? I
would think that in the case of documentation the answer is "yes", but
I can't help but feel slightly silly about reporting cases like this.
--
Peter Geoghegan http://www.2ndQuadrant.com/
Postg
On 29 January 2012 21:19, Peter Geoghegan wrote:
> Is it really that much of a problem to create a new severity level for
> this stuff?
I should probably have quoted this refinement, which was part of the
discussion that I originally quoted Robert from:
On 24 November 2011 16:55, Alvaro H
the log
> to enable the DBA to figure out that the first error message is likely
> nothing more serious than an integrity constraint doing its bit to
> preserve data integrity, while the second is likely a sign of
> impending disaster.
Is it really that much of a problem to creat
, "could not find plan for CTE \"%s\"", rte->ctename)
(which would necessitate creating a new severity level, INTERNAL_ERROR).
So that DBAs could find these kinds of problems systematically. This
is an error message that we expect no one to see.
--
Peter Geoghegan
like an integrity constraint violation. I
continue to maintain that we should have a new severity level for this
sort of thing.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
here:
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chan
I noticed the following in the auto_explain documentation:
"This can have extremely negative impact on performance."
Surely it should say:
"This can have an extremely negative impact on performance."
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Devel
On 20 January 2012 02:53, Robert Haas wrote:
> OK, done.
Thanks
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
h
On 17 January 2012 01:37, Robert Haas wrote:
>> It's a fairly inconsequential bug, but it is worth fixing...
>
> Fixed.
Thanks.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing
On 9 January 2012 18:47, Robert Haas wrote:
> On Sat, Dec 31, 2011 at 8:54 PM, Peter Geoghegan
> wrote:
>> ISTM that the following reference, at config.sgml line 1345, ought to
>> be adjusted due to the introduction of the new checkpointer process:
>>
>>
ISTM that the following reference, at config.sgml line 1345, ought to
be adjusted due to the introduction of the new checkpointer process:
Setting this to zero disables
background writing (except for checkpoint activity).
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL
On 20 December 2011 18:11, Tom Lane wrote:
> Simon Riggs writes:
>> On Tue, Dec 20, 2011 at 5:50 PM, Peter Geoghegan
>> wrote:
>>> In fact, that macro is defined in access/htup.h...should it be?
>
>> IMHO comment is wrong, code is in the right place.
>
>
Line 834 of heapam.c has the following comment:
/*
* This is formatted so oddly so that the correspondence to the macro
* definition in access/heapam.h is maintained.
*/
In fact, that macro is defined in access/htup.h...should it be?
--
Peter Geoghegan http://www.2ndQuadrant.com
On 11 December 2011 17:53, Cihan ŞENGÜL wrote:
> Hi
> Libpqwce are published. Gösterilemiyor.Bana reference to VB NET 2003. NET
> 2003, I can reference the DLL required for VB
I don't understand.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Sup
inCE libpq port very successfully. I built it
from source too, as there were binary compatibility problems with some
of the ARM devices that had custom WinCE kernels (not uncommon - WinCE
is available under a "shared source" agreement), but not others that
didn't.
What'
ot;severe error".
>
> +1
+1
On reflection, that's better than what I proposed.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
INTERNAL_ERROR),
464:(errcode(ERRCODE_INTERNAL_ERROR),
526:(errcode(ERRCODE_INTERNAL_ERROR),
A new severity level is called for. In addition, if we had a new
severity level, the footprint wouldn't be too bad on all those legacy
elog() calls as compa
I noticed this typo in a comment in the file nbtsort.c:
/*
* We need to log index creation in WAL iff WAL archiving/streaming is
* enabled UNLESS the index isn't WAL-logged anyway.
*/
I suggest an s/iff/if/
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development,
On 29 September 2011 23:15, Tom Lane wrote:
> Peter Geoghegan writes:
>> I've built Postgres from master, and found that the following fairly
>> simple query breaks:
>
>> select count(*)
>> from
>> (
>> select
>> schemaname
>&g
On 29 September 2011 21:59, Merlin Moncure wrote:
> hm -- works for me (9.1.0)
It works for me on REL9_1_STABLE too, unsurprisingly, as I would think
it highly unlikely that such a glaring bug would slip into a stable
release.
--
Peter Geoghegan http://www.2ndQuadrant.com/
Postgre
e "no relation entry for relid
1". Why is that?
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
37 matches
Mail list logo
