[BUGS] BUG #6120: Problem running post-install step in Mac OS X Lion (GM)

2011-07-17 Thread Paula Andrea Carvajal

The following bug has been logged online:

Bug reference:  6120
Logged by:  Paula Andrea Carvajal
Email address:  paanc...@gmail.com
PostgreSQL version: 9.0.4
Operating system:   Mac OS X 10.7 (GM)
Description:Problem running post-install step in Mac OS X Lion (GM)
Details: 

Problem using EnterpriseDB Mac OS X Installer version Version 9.0.4-1 (from
http://www.enterprisedb.com/products-services-training/pgdownload).

Error message:
Problem running post-install step. Installation may not complete correctly
La inicialización del clúster de la base de datos falló.

MacBook 13-inch, Aluminum, Late 2008
Procesador 2 GHz Intel Core 2 Duo
Memoria 8 GB 1333 MHz DDR3
Pantalla Color LCD integrada 13 pulgada(s) (1280 x 800)
Gráficos NVIDIA GeForce 9400M 256 MB
Software Mac OS X Lion 10.7 (11A511)

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


Re: [BUGS] Spurious errors relating to escaped single quotes

2011-07-17 Thread Gavin Flower

On 16/07/11 05:21, Tom Lane wrote:

Gavin Flower  writes:

On 15/07/11 11:25, Gavin Flower wrote:

I think it should be possible to put a constraint on the master table
to prevent rows being inserted.

Of course, minutes after I sent the above - I realized these constraints
are inherited, so the above is nonsense!  :-(

Yeah.  I think there's been some discussion of inventing a non-inherited
variety of check constraint, so that you could put something like
"CHECK (false) NO INHERIT" on the parent table.  There's not really
consensus for this though.

IMO we'd be better advised to spend our time on building an explicit
partitioning mechanism to handle the common cases more simply and
efficiently, instead of continuing to add frammishes to the inheritance
mechanism.

regards, tom lane


How about being able to mark individual columns, and optionally the
table itself, as ABSTRACT?

Though, I agree that a proper partitioning mechanism would be better.

Cheers,
Gavin


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


[BUGS] BUG #6121: error msg feature request for initial server tasks

2011-07-17 Thread Thomas Pitschel

The following bug has been logged online:

Bug reference:  6121
Logged by:  Thomas Pitschel
Email address:  th.pitsc...@web.de
PostgreSQL version: pgAdmin 1.12.3
Operating system:   Windows
Description:error msg feature request for initial server tasks
Details: 

Hello,

thanks very much for this great db package.

On connecting to an older Postgresql server one gets this typical msg:

>>
Server instrumentation

The server lacks instrumentation functions. 

pgAdmin III uses some support functions that are not available by default in
all PostgreSQL versions. These enable some tasks that make life easier when
dealing with log files and configuration files. 

The adminpack is installed and activated by default if you are running the
'official' pgInstaller distribution of PostgreSQL for Windows and is
included as a contrib module with all versions of PostgreSQL 8.2 and above.
However, if you are running any other ...
<

This should better read along the lines (CAPITALS for emphasis):

"Server instrumentation

The server lacks instrumentation functions.
 
pgAdmin III uses some support functions that are not available by default in
all PostgreSQL SERVER versions. These enable some tasks that make life
easier when dealing with log files and configuration files.

TO ADD THOSE CAPABILITIES, AN ADMINPACK CAN BE INSTALLED ON THE SERVER.
 
The adminpack is installed and activated by default if you are running the
'official' pgInstaller distribution of PostgreSQL for Windows and is
included as a contrib module with all versions of PostgreSQL 8.2 and above.
However, if you are running any other ... "

It is further good to explain what you loose when not installing the
adminpack.



Many thanks

Thomas

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs