Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Marek wrote:
>> createdb: database creation failed: ERROR: encoding LATIN2 does not match
>> server's locale pl_PL.UTF-8
>> The server's LC_CTYPE setting requires encoding UTF8.
> That's intentional. You're trying to use a UTF-8 locale, with LATIN2
NikhilS <[EMAIL PROTECTED]> writes:
> This can be handled by setting index->isconstraint appropriately inside
> generateClonedIndexStmt().
Done.
> The fundamental question though is should we allow primary, unique
> CONSTRAINTS which use the index mechanism just as an implementation to be
> creat
"christopher wood" <[EMAIL PROTECTED]> writes:
> 1. Should I not have received an e-mail of your reply, asking for an
> example?
Yup, in fact two of them: one copy direct and one via the mailing list.
You need to check into possible over-aggressive spam filtering at your
end.
Hi Tom,
I reported this bug a few days ago, and did not receive any follow up
e-mail,
but then, by shear coincidence Dean Rasheed referred the following two links
to me.
http://archives.postgresql.org/pgsql-bugs/2007-11/msg00323.php
http://archives.postgresql.org/pgsql-committers/2007-11/msg0
"Architekt Schalbruch" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED]:~/data> pg_ctl reload
> pg_ctl: kein Datenbankverzeichnis angegeben und Umgebungsvariable PGDATA
> nicht gesetzt
This isn't a bug --- you have not told pg_ctl where the postgres data
directory is.
regar
Berichten Sie Fehler an .
[EMAIL PROTECTED]:~/data> pg_ctl reload
pg_ctl: kein Datenbankverzeichnis angegeben und Umgebungsvariable PGDATA
nicht gesetzt
Database though still runs after that, but e.g. the new logfile name is not
regarded
Sincerely
Bernd Schalbruch
ArchiTect / WebTect
