On 11/23/2011 02:02 PM, nadhiya wrote:
The following bug has been logged online:
Bug reference: 6305
Logged by: nadhiya
Email address: nadhiyacs...@gmail.com
PostgreSQL version: 8.4
Operating system: ubuntu 10.04
Description:cann't reinstall postgresql
Details:
i i
Excerpts from Peter Eisentraut's message of jue nov 24 19:01:04 -0300 2011:
> On ons, 2011-11-23 at 12:07 +0100, Marco Bernasocchi wrote:
> > Hi all, porting QGIS to android I ported libpq as well, I had to modify
> > two files to successfully compile it without-readline. I attach the two
> > ne
The following bug has been logged online:
Bug reference: 6307
Logged by: Maksym Boguk
Email address: maxim.bo...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Linux
Description:intarray extention gin index does not work with Hot
standby
Details:
Intarray gin
On ons, 2011-11-23 at 12:07 +0100, Marco Bernasocchi wrote:
> Hi all, porting QGIS to android I ported libpq as well, I had to modify
> two files to successfully compile it without-readline. I attach the two
> needed minor patches. further informations can be found at android.qgis.org.
The Postg
On tor, 2011-11-24 at 11:14 -0500, Robert Haas wrote:
> So I would propose to steer clear of the word "internal", because the
> really scary errors typically are not internal to PostgreSQL at all.
> What I think we want to distinguish between is things that are
> PEBKAC/GIGO, and everything else.
Excerpts from Marco Bernasocchi's message of mié nov 23 08:07:05 -0300 2011:
> Hi all, porting QGIS to android I ported libpq as well, I had to modify
> two files to successfully compile it without-readline. I attach the two
> needed minor patches. further informations can be found at android.qg
On 24 November 2011 16:55, Alvaro Herrera wrote:
>
> Excerpts from Robert Haas's message of jue nov 24 13:14:38 -0300 2011:
>
>> What I think we want to distinguish between is things that are
>> PEBKAC/GIGO, and everything else. In other words, if a particular
>> error message can be caused by ty
Excerpts from Robert Haas's message of jue nov 24 13:14:38 -0300 2011:
> What I think we want to distinguish between is things that are
> PEBKAC/GIGO, and everything else. In other words, if a particular
> error message can be caused by typing something stupid, unexpected,
> erroneous, or whatev
On Wed, Nov 23, 2011 at 7:19 AM, Peter Geoghegan wrote:
> On 23 November 2011 02:49, Robert Haas wrote:
>> There is no sort of systematic labeling of error messages in the log
>> to enable the DBA to figure out that the first error message is likely
>> nothing more serious than an integrity const
On 24.11.2011 11:44, kara...@kommespaeter.de wrote:
PostgreSQL version: 8.4
...
Selecting (nonexistant) column 'name' or 'varchar' results in an error.
Selecting qualified nonexistant columns 'name' or 'varchar', you get the
record as record. The view definition shows * casted to name or varchar.
On 24.11.2011 12:23, Heikki Linnakangas wrote:
On 22.11.2011 23:18, Robert Balser wrote:
The following bug has been logged online:
Bug reference: 6304
Logged by: Robert Balser
Email address: robert.bal...@hp.com
PostgreSQL version: 9.0.5
Operating system: HPUX 11.31 ia64
Description: initdb fa
The following bug has been logged online:
Bug reference: 6306
Logged by:
Email address: kara...@kommespaeter.de
PostgreSQL version: 8.4
Operating system: Windows XP
Description:sql parser: weird behaviour when selecting
tablename.'name' from a table
Details:
Select
On 22.11.2011 23:18, Robert Balser wrote:
The following bug has been logged online:
Bug reference: 6304
Logged by: Robert Balser
Email address: robert.bal...@hp.com
PostgreSQL version: 9.0.5
Operating system: HPUX 11.31 ia64
Description:initdb fails with loale ko_KR
13 matches
Mail list logo
