Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I do think we need a boolean for start/stop of archiving, rather than
setting it to '' to turn it off. Tom, I think the group agreed to this
on clarity grounds.
I didn't see any consensus there, nor do I see a point to it.
I saw a
All that is then needed is to teach each binary to link in
win32ver.o.
For initdb, I've done this like:
ifeq ($(PORTNAME), win32)
FILEDESC=initdb - initialize a new database cluster
OBJS+=win32ver.o
endif
I assume what you would like is to have just the FILEDESC
row in there?
Bruce Momjian wrote:
I talked to Tom about this today. First, I want to apologize for
running you around in circles in this. I don't think we are giving it
the attention it needs because of our schedule. I also think the
functionality is drifting into the new features territory and this is
also
All messages translated and fixed. Thanks.
libpq-zh_TW.po
Description: Binary data
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Magnus Hagander said:
One more thing I realised - we need two different types of versioninfo
structures, because one fields tells wether it's a DLL or an app. How
would you prefer this done - either using $(WIN32VERDLL)/$(WIN32VERAPP)
(or $(PORTOBJSHLIB)/$(PORTOBJAPP) if we go down that
One more thing I realised - we need two different types of
versioninfo
structures, because one fields tells wether it's a DLL or
an app. How
would you prefer this done - either using
$(WIN32VERDLL)/$(WIN32VERAPP) (or
$(PORTOBJSHLIB)/$(PORTOBJAPP) if we
go down that route), or
Oh, and for the record, we version libpq.dll on windows in the 7.x.y
manner, and have been doing so ever since we first added
win32 support.
We can't really back that one down, so we'd need an
exception for that
one.
This one *does* matter, because it's the main library other
Am Sonntag, 27. Juni 2004 09:44 schrieb Dennis Bjorklund:
On Sun, 27 Jun 2004, Dennis Bjorklund wrote:
Here is a trivial fix for some error messages that was not translated
before. I've also gotten rid of some cut and paste of strings. That
doesn't always work (like in this case) when
Am Donnerstag, 29. Juli 2004 14:46 schrieb Magnus Hagander:
2) We'll *have* to start actually bumping at least minor versions
whenever we change the code in a sharaed lib. Which we don't do now,
except for libpq. For example, plperl still says 0.0, and plpgsql says
1.0. Also, all the
[ CC to patches.]
Yep, that is a bug. Patch attached and applied.
---
Sean Chittenden wrote:
Uh, this patch is strange:
-#define WHITESPACE \f\n\r\t\v/* as defined by
isspace() */
+#define
Done.
---
Devrim GUNDUZ wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Attached files are the up2date versions of Turkish FAQ. Could you please
apply them to CVS?
Regards,
- --
Devrim GUNDUZ
Andreas Pflug wrote:
So, I suggest we get the logging code into the backend, and you can code
anything you want pgadmin to do in plperlu, and Win32 supports plperlu
too. The big advantage is that you can improve the plperlu functions
with every release of pgadmin.
I do not agree on
Bruce Momjian wrote:
I do think we need a boolean for start/stop of archiving, rather than
setting it to '' to turn it off. Tom, I think the group agreed to this
on clarity grounds. I would like the server to throw an error if you
try to turn on archiving and the command is set to ''.
Let
Bruce Momjian wrote:
Basically I think we are converging on an answer that we can't do any of
this for 7.5.
If it's not going into the distribution as contrib or core, I'll package
that as additional admin pack. I'm quite sure I can convince the win32
installer packager guys to include that as
Bruce Momjian [EMAIL PROTECTED] writes:
Now, if you say people will rarely turn archiving on/off, then one
parameter seems to make more sense.
I really can't envision a situation where people would do that. If you
need PITR at all then you need it 24x7.
regards, tom
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Now, if you say people will rarely turn archiving on/off, then one
parameter seems to make more sense.
I really can't envision a situation where people would do that. If you
need PITR at all then you need it 24x7.
OK, then we are
Andreas Pflug [EMAIL PROTECTED] writes:
Bruce Momjian wrote:
So, I suggest we get the logging code into the backend, and you can code
anything you want pgadmin to do in plperlu, and Win32 supports plperlu
too. The big advantage is that you can improve the plperlu functions
with every release
Attached is a patch that fixes the owner change command on objects that
have privileges.
It probably needs a once over review since it involves a decent amount
of pointer arithmetic.
Note that languages don't have owners, and hence don't need fixing.
The owner change acl support is as follows:
All messages translated.
Thanks!
initdb-zh_TW.po
Description: Binary data
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
All messages fixed.
Thanks.
pg_controldata-zh_TW.po
Description: Binary data
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
All messages translated.
Thank you.
pg_ctl-zh_TW.po
Description: Binary data
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
All messages translated.
Thanks.
pg_resetxlog-zh_TW.po
Description: Binary data
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Magnus Hagander wrote:
Perhaps a compromise would be to set versioninfo on libpq.dll (which
we alerady do), and on all the EXEs, and ignore the rest of the DLLs.
It's not ideal, but it's a great deal better than nothing at all.
If that is an option, why not just put versions into the
Zhenbang Wei wrote:
All messages translated.
Installed, including the subsequent ones.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
24 matches
Mail list logo
