Hello, Pgsql-bugs.
According to the "Moving tablespaces" thread started by Bruce
http://archives.postgresql.org/pgsql-docs/2011-12/msg3.php
pg_tablespace.spclocation column is removed in the 9.2beta. However
this breaks backward compatibility for a bunch of products, e.g.
pgAdmin, phpPgAdmin,
Hello, r.
You wrote:
rd> When I do this
rd> CREATE TABLE "T1"
rd> (
rd> "T1_ID" bigint NOT NULL,
rd> CONSTRAINT "T1" PRIMARY KEY ("T1_ID" )
rd> );
rd> I get the following message:
rd> NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "T1" for
table "T1"
rd> ERROR: relation "
Hello, Tom.
You wrote:
TL> Robert Haas writes:
>> On Tue, Nov 15, 2011 at 5:16 AM, Heikki Linnakangas
>> wrote:
>>> NEW used to be a reserved keyword, but it's not so in 9.0 anymore. So 9.0
>>> pg_dump thinks it doesn't need to be quoted.
>> Why isn't it correct?
TL> It's correct to not quote
Hello, Laurian.
You wrote:
LV> The following bug has been logged online:
LV> Bug reference: 6279
LV> Logged by: Laurian Vostinar
LV> Email address: lvosti...@servoy.com
LV> PostgreSQL version: 9.0
LV> Operating system: Windows 7
LV> Description:quoting needed for co
Hello, Robert.
You wrote:
RH> On Tue, Jul 5, 2011 at 11:37 AM, Pavel Golub wrote:
>> RH> Yeah. In particular, it conflicts with the ancient copy syntax which
>> RH> we still support for backwards compatibility with versions < 7.3. We
>> RH> can fix the imme
Hello, Robert.
You wrote:
RH> On Tue, Jul 5, 2011 at 11:06 AM, Alvaro Herrera
RH> wrote:
>> Excerpts from Pavel Golub's message of mar jul 05 10:52:06 -0400 2011:
>>> Hello.
>>>
>>> System: PostgreSQL v9.0 Windows XP SP3
>>> SQL: COPY "tablename" TO STDOUT WITH (FORMAT binary)
>>> ERROR: syntax
Hello, Alvaro.
You wrote:
AH> Excerpts from Pavel Golub's message of mar jul 05 10:52:06 -0400 2011:
>> Hello.
>>
>> System: PostgreSQL v9.0 Windows XP SP3
>> SQL: COPY "tablename" TO STDOUT WITH (FORMAT binary)
>> ERROR: syntax error at or near "binary"
>> LINE 1: ...OPY "tablename" TO STDOUT
Hello.
System: PostgreSQL v9.0 Windows XP SP3
SQL: COPY "tablename" TO STDOUT WITH (FORMAT binary)
ERROR: syntax error at or near "binary"
LINE 1: ...OPY "tablename" TO STDOUT WITH (FORMAT binary)
^
** Error **
ERROR: syntax erro
Hello, Kevin.
You wrote:
KG> Heikki Linnakangas wrote:
KG>
>> Manual says (at the bottom of
>> http://www.postgresql.org/docs/8.4/static/app-pgdump.html):
>>
>>> To specify an upper-case or mixed-case name in -t and related
>>> switches, you need to double-quote the name; else it will be
>>>
Hello, Tom.
You wrote:
TL> Pavel Golub writes:
>> TL> I'm not sure what distinction you're trying to draw. Do you want us to
>> TL> add a close() just before exit()? If so, what for?
>> First of all, for uniformity I guess. :) .backup files are closed
>
Hello, Tom.
You wrote:
TL> "Pavel Golub" writes:
>> pg_restore doesn't close input .tar archive file after restore process.
>> However, file is closed after pg_restore termination, I suppose it's not
>> correct behaviour.
TL> I'm not sure wha
The following bug has been logged online:
Bug reference: 5451
Logged by: Pavel Golub
Email address: pa...@microolap.com
PostgreSQL version: 8.4.x
Operating system: Windows
Description:pg_restore doesn't close input .tar archive
Details:
pg_restore doesn&#x
Hello, Tom.
You wrote:
TL> Pavel Golub writes:
>> Example:
>> CREATE OR REPLACE FUNCTION test_char_function()
>> RETURNS TABLE(id int, salesourcecode character) AS
>> $BODY$
>> VALUES (1, 'one'), (2, 'two'), (3, 'three');
>&
Hello, Pgsql-bugs.
PostgreSQL version: 8.4.x
Operating system: All
If RETURNS TABLE clause of CREATE FUNCTION contain column of character type
(withou
length specifier) it should be treated as character(1) according to
manual, but it look like text.
(http://www.postgresql.org/docs/8.4/static/d
Hello, Oscar.
First of all you shouldn't post such messages here since this is not a
bug for sure.
Take a look on MicroOLAP Database Designer for PostgreSQL at
http://microolap.com/products/database/postgresql-designer/
You will be surprised :)
You wrote:
OMAE> The following bug has been logge
4662
PG> Logged by: Pavel Golub
PG> Email address: pavel.go...@gf.microolap.com
PG> PostgreSQL version: 8.4
PG> Operating system: Windows XP SP3
PG> Description:make failed using MinGW under WinXP
PG> Details:
PG> $ make
PG> We got an error:
PG>
The following bug has been logged online:
Bug reference: 4662
Logged by: Pavel Golub
Email address: pavel.go...@gf.microolap.com
PostgreSQL version: 8.4
Operating system: Windows XP SP3
Description:make failed using MinGW under WinXP
Details:
$ make
We got an
Hello, Tom.
Thank a lot Tom.
Just curious, what was the reason?
Regards
You wrote:
TL> "Pavel Golub" <[EMAIL PROTECTED]> writes:
>> Comparing 8.3.1 to 8.2.5 release INSERT of >1000 rows is very slow.
>> INSERT INTO numbers (numberint, numberstr) VALUES
The following bug has been logged online:
Bug reference: 4079
Logged by: Pavel Golub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Windows XP SP2
Description:libpq.dll very slow (unusable)
Details:
Comparing 8.3.1 to 8.2.5 release
The following bug has been logged online:
Bug reference: 3909
Logged by: Pavel Golub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3RC2
Operating system: WinXP
Description:src\tools\msvc\clean.bat clears parse.h file
Details:
Executing clean.bat from src
Hello, Bruno.
This is not an PostgreSQL team product, But MicroOLAP!
Use MicroOLAP support system to solve this!
You wrote:
B> The following bug has been logged online:
B> Bug reference: 2995
B> Logged by: Bruno
B> Email address: [EMAIL PROTECTED]
B> PostgreSQL version: 8.2.
t;shouldn't" be used, rather than prohibited.
BM> -------
BM> Pavel Golub wrote:
>>
>> The following bug has been logged online:
>>
>> Bug reference: 2852
>> Logged by:
The following bug has been logged online:
Bug reference: 2852
Logged by: Pavel Golub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.x
Operating system: Windows XP
Description:User-defined type name begins with the underscore
character (_) can be created
Hello, pgsql-bugs.
Documentation says:
"User-defined type names cannot begin with the
underscore character (_) and can only be 62
characters long (or in general NAMEDATALEN - 2,
rather than the NAMEDATALEN - 1 characters
allowed for other names). Type names beginning
with underscore are reserved f
The following bug has been logged online:
Bug reference: 2570
Logged by: Pavel Golub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.x
Operating system: Windows XP
Description:Connection closed unexpectedly
Details:
Bug may be reproduced by any tool using
The following bug has been logged online:
Bug reference: 2377
Logged by: Pavel Golub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Windows XP
Description:pg_constraint didnt't updated when table columns deleted
Details:
To illus
26 matches
Mail list logo
