Sincerely,
--
Richard van den Berg, CISSP
---
Trust Factory B.V. | www.dna-portal.net
Bazarstraat 44a| www.trust-factory.com
2518AK The Hague | Phone: +31 70 3620684
The Netherlands
an still use 'psql -f
foo.sql' safely.
Sincerely,
--
Richard van den Berg, CISSP
---
Trust Factory B.V. | www.dna-portal.net
Bazarstraat 44a| www.trust-factory.com
2518AK The Hague | Phone: +31 70 3620684
The Netherlands| Fax
gt; Win32 PostgreSQL 8 database, assuming you install the base Cygwin
> environment.
I don't like the idea of running a different version of the client and
server, but the thought did cross my mind. I think I'll stick with the
cmd.exe terminal inst
topped. Using the -l option of pg_ctl
also does not help.
Is there a way for this setup to work,
without the dos box being visable all the time? I use system logging, so
I don't need the stdout/stderr of pg_ctl.
Sincerely,
Richard van den Berg, CISSP
-
es, I need to enter the password in the service definition. Even
when the user postgres is logged on and wants to start the service. I don't
want my password to be stored in the registry, so I am still stuck. *sigh*
All this hassle for what in unix would only require
the addition of a sing
oin pg_autovacuum c
on a.oid = c.vacrelid
where a.relkind = 'r'
and schemaname not like 'pg_temp_%%'
and a.oid not in (select distinct vacrelid from
pg_autovacuum);
update pg_
r start
or in the postgresql.conf
file.
Richard van den Berg, CISSP
---
Trust Factory B.V. | www.dna-portal.net
Bazarstraat 44a | www.trust-factory.com
2518AK The Hague | Phone: +31 70 3620684
The Netherlands | Fax : +31 70 3603009
---
' that threw me off. In my mind, it should
read:
This option can be set at server start or in the postgresql.conf
file during runtime.
Sincerely,
Richard van den Berg, CISSP
---
Trust Factory B.V. | www.dna-portal.net
Bazarstraat 44a | www.tru
"_dir". Postgres
treats the first one as a wildcard, but not the second one. Strangely
enough both characters are in the ISO-8859-1 table: 0xEC and 0xFD.
Sincerely,
--
Richard van den Berg, CISSP
---
Trust Factory B.V. | www.dna-portal.net
base files.
Is there a good reason that the official RPM on postgresql.org is not
build with HAVE_INT64_TIMESTAMP ? It would have been so nice if this
would have worked. :-/
Sincerely,
--
Richard van den Berg, CISSP
---
Trust Factory B.V. | www.dna-
x27;ll just do a pg_dump / pg_restore cycle, as I was planning to do. Is
there any guarantee for compatability the pg_dump format? Say, can a
8.1.0 pg_dump made using a 64 bit Solaris SPARC binary be read using a
32 bit Intel Linux pg_restore 8.1.0 binary? ;-)
--
Richard van
sometime next week).
Sincerely,
Richard van den Berg
2 comes out. The full answer
is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342369
For the Debian bug track system, the full discussion on the postgresql
mailing list starts here:
http://archives.postgresql.org/pgsql-general/2005-12/msg00367.php
Thanks everyone for clearing this up.
Sincer
13 matches
Mail list logo
