Josh Kupershmidt writes:
> I noticed that configuring Postgres with a BLCKSZ smaller than default
> was causing 'make check' give an interesting error on git head.
> [ spgist regression test fails ]
Ugh.
> I'm not sure what'd be the right
> way to fix this after reading the comment above
> SPGIS
Hi all,
I noticed that configuring Postgres with a BLCKSZ smaller than default
was causing 'make check' give an interesting error on git head. You
should be able to see this with a simple:
./configure --enable-debug --enable-cassert --with-blocksize=4 &&
make check
which, among a few other s
The following bug has been logged on the website:
Bug reference: 6706
Logged by: Maciek Sakrejda
Email address: m.sakre...@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Ubuntu 12.04 LTS (3.2.0-25-generic x86_64)
Description:
Using the 9.2beta2 o
On 06/25/2012 11:10 PM, Dave Page wrote:
On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer wrote:
Dave: Is there any chance the installers link to that page from their error
dialogs, or a static-and-sanitised version of it in docs? If you're ok
updating the installer messages I'll collect up a sani
On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer wrote:
>
> Dave: Is there any chance the installers link to that page from their error
> dialogs, or a static-and-sanitised version of it in docs? If you're ok
> updating the installer messages I'll collect up a sanitized version that
> doesn't link to
On Mon, Jun 25, 2012 at 9:57 AM, Tom Lane wrote:
> Merlin Moncure writes:
>> 2012-06-25 09:08:08 CDT [postgres@ysanalysis_hes]: LOG: could not
>> send data to client: Broken pipe
>> 2012-06-25 09:08:10 CDT [postgres@ysanalysis_hes]: LOG: unexpected
>> EOF on client connection
>> 2012-06-25 09:0
Merlin Moncure writes:
> 2012-06-25 09:08:08 CDT [postgres@ysanalysis_hes]: LOG: could not
> send data to client: Broken pipe
> 2012-06-25 09:08:10 CDT [postgres@ysanalysis_hes]: LOG: unexpected
> EOF on client connection
> 2012-06-25 09:08:10 CDT [postgres@ysanalysis_hes]: LOG: process 22821
>
I got a crash on a production server this morning following during
very heavy load. This is postgres 9.1.3 on Linux (going to 9.1.4
asap). I didn't catch a core dump it doesn't look like one would help
anyways. Server is virtualized quad on vmware. Here is the log I
have:
2012-06-25 09:07:45
On Mon, Jun 25, 2012 at 3:46 PM, Tom Lane wrote:
> Pavel Golub writes:
>> I'm aware of problems caused by this hard coded column. My proposal is
>> to convert pg_tablespace to system view may be?
>
> It's not that easy to make a 100% backwards compatible view for a system
> catalog. The main sti
Pavel Golub writes:
> I'm aware of problems caused by this hard coded column. My proposal is
> to convert pg_tablespace to system view may be?
It's not that easy to make a 100% backwards compatible view for a system
catalog. The main sticking point is the OID column; see recent problems
with pg_
10 matches
Mail list logo
