Craig Ringer writes:
> PostgreSQL 9.1 isn't compatible with databases from 8.3, so you can't
> actually run Pg 9.1 directly against a datadir from 8.3; that's why I
> suggested the latest 8.3 point release.
> However, your startup should be failing with a message telling you this,
> not with a
On 07/13/12 6:00 AM, tsial...@gmail.com wrote:
PANIC: 42501: could not open control file "global/pg_control": Permission
denied
start a CMD prompt ('dos') via 'run as admin'.
from this privileged command window,
CACLS \path\to\pg\data /T /E /G pss-svc:(OI)(CI)F
then try restarting postgr
On 07/14/2012 12:18 AM, Petros Tsialiamanis wrote:
Thank you very much for your reply.
Thanks for coming back and re-testing with a modern PostgreSQL.
PostgreSQL 9.1 isn't compatible with databases from 8.3, so you can't
actually run Pg 9.1 directly against a datadir from 8.3; that's why I
su
On ons, 2012-07-11 at 11:32 +0200, Christian Ullrich wrote:
> 61 #: pg_basebackup.c:127
>62 #, c-format
>63 msgid " -F, --format=p|t output format (plain, tar)\n"
>64 msgstr " -F, --format=c|t|p Ausgabeformat (plain, tar)\n"
>
> pg_basebackup does not support "c" format
On Fri, Jul 13, 2012 at 4:11 PM, Tom Lane wrote:
> Daniele Varrazzo writes:
>> Wouldn't it be better to call the indexes NEWTABLE_OLDINDEXNAME?
>
> Then the CREATE LIKE command would fail altogether if that name were
> already taken. Postponing the selection of the index name to the time
> when
On 07/13/2012 09:00 PM, tsial...@gmail.com wrote:
The following bug has been logged on the website:
Bug reference: 6735
Logged by: Petros Tsialiamanis
Email address: tsial...@gmail.com
PostgreSQL version: 8.3.5
Operating system: WinXP Pro SP3
Description:
Hi,
The first time
Daniele Varrazzo writes:
> Wouldn't it be better to call the indexes NEWTABLE_OLDINDEXNAME?
Then the CREATE LIKE command would fail altogether if that name were
already taken. Postponing the selection of the index name to the time
when DefineIndex runs is really the only safe thing.
Ryan Kelly writes:
> The comments on chooseIndexName in src/backend/parser/parse_utilcmd.c say:
> * XXX this is inherently broken because the indexes aren't created
> * immediately, so we fail to resolve conflicts when the same name is
> * derived for multiple indexes.
> Which looks like the cas
On Fri, Jul 13, 2012 at 2:24 PM, Ryan Kelly wrote:
> On Fri, Jul 13, 2012 at 12:00:14PM +, daniele.varra...@gmail.com wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 6734
>> Logged by: Daniele Varrazzo
>> Email address: daniele.varra...@gmail
The following bug has been logged on the website:
Bug reference: 6735
Logged by: Petros Tsialiamanis
Email address: tsial...@gmail.com
PostgreSQL version: 8.3.5
Operating system: WinXP Pro SP3
Description:
Hi,
The first time I started the postgresql server as 'Local
The following bug has been logged on the website:
Bug reference: 6736
Logged by: Maksym Boguk
Email address: maxim.bo...@gmail.com
PostgreSQL version: 9.0.4
Operating system: FreeBSD
Description:
Hi,
May be it was fixed in more recent releases, but I can not find rel
On Fri, Jul 13, 2012 at 12:00:14PM +, daniele.varra...@gmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6734
> Logged by: Daniele Varrazzo
> Email address: daniele.varra...@gmail.com
> PostgreSQL version: 9.1.4
> Operating system: Lin
The following bug has been logged on the website:
Bug reference: 6734
Logged by: Daniele Varrazzo
Email address: daniele.varra...@gmail.com
PostgreSQL version: 9.1.4
Operating system: Linux
Description:
Weird, isn't it? Test case below.
Dropping the comment, the cre
On 07/13/2012 05:19 PM, Mirko Mittmann wrote:
Hello,
the message from the event viewer says the following things:
anwendungsname postgres.exe
fehlermodulname SSLEAY32.dll
fehlermodulversion 6.0.6002.18541
Please reply to pgsql-bugs@postgresql.org not directly to me. Sorry, I
forgot to set R
14 matches
Mail list logo
