Am Samstag, den 29.03.2008, 12:25 + schrieb [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Feb 23, 2008 at 01:13:38PM +0100, Mathias Hasselmann wrote:
[...]
Avahi/Bonjour/DNS-SD support[1] is very important, for integrating
Postgresql with modern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 01, 2008 at 09:35:56AM +0200, Mathias Hasselmann wrote:
Am Samstag, den 29.03.2008, 12:25 + schrieb [EMAIL PROTECTED]:
[...]
Sorry for a dumb question, but I couldn't figure that out from your
references [1]..[4]: does that mean
This follows up on the discussion in
http://archives.postgresql.org/pgsql-hackers/2008-03/msg01033.php
- pg_ctl will refuse a smart shutdown during online backup.
- The postmaster will also refuse to shutdown in smart mode
in that case and log a message to that effect.
- In fast shutdown mode,
Folks,
please find attached a patch which implements psql command aliases. They
work the same way as on bash, zsh and others, for example:
#= \alias d \dt+
#= \d
List of relations
Schema | Name | Type | Owner | Description
+--+---+---+-
public |
Am Dienstag, den 01.04.2008, 12:02 + schrieb [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 01, 2008 at 09:35:56AM +0200, Mathias Hasselmann wrote:
Am Samstag, den 29.03.2008, 12:25 + schrieb [EMAIL PROTECTED]:
[...]
Sorry for a dumb question, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 01, 2008 at 05:07:31PM +0200, Mathias Hasselmann wrote:
[...]
Personally, I'be rather scared than delighted ;-)
So in data centers you don't even trust the machines in your broadcast
domain?
Kind of. Put it another way: never have
Bernd Helmle [EMAIL PROTECTED] writes:
please find attached a patch which implements psql command aliases. They
work the same way as on bash, zsh and others, for example:
#= \alias d \dt+
#= \d
Do we really want such a thing? The space of backslash command names
is so densely populated
Am Dienstag, 1. April 2008 schrieb Tom Lane:
Do we really want such a thing?
Yes!
The space of backslash command names
is so densely populated already that it's hard to imagine creating
aliases without conflicting with existing (or future) command names
--- as indeed your example does. It
--On Dienstag, April 01, 2008 11:39:59 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Do we really want such a thing?
Well, i use aliases everytime and everywhere they got implemented and i
found it quite useful to _extend_ existing behavior (integrating additional
functionality in an easy way)
On Thu, 2008-03-27 at 17:34 +, Simon Riggs wrote:
Follow-up during March 2008 CommitFest
On Thu, 2007-06-07 at 21:53 +0100, Simon Riggs wrote:
On Sat, 2007-03-31 at 00:51 +0200, Florian G. Pflug wrote:
- pg_stop_backup() will wait until the WAL file that ends the backup is
safely
On Tue, 2008-04-01 at 15:34 +0200, Albe Laurenz wrote:
This follows up on the discussion in
http://archives.postgresql.org/pgsql-hackers/2008-03/msg01033.php
- pg_ctl will refuse a smart shutdown during online backup.
- The postmaster will also refuse to shutdown in smart mode
in that
On Tue, 2008-04-01 at 17:42 +0100, Simon Riggs wrote:
Few comments:
* smart shutdown waits for sessions to complete, yet this just ignores
smart shutdowns which is something a little different. I think we
should wait for the backup to complete and then shutdown.
* The #defines at top of
On Tue, Apr 01, 2008 at 12:58:44AM -0400, Tom Lane wrote:
Gregory Stark [EMAIL PROTECTED] writes:
One --perhaps nice, perhaps not-- property of this is that if
you defined a function named rtrim and then did \df rtrim it
would show you _both_ the system and user function and make it
David Fetter [EMAIL PROTECTED] writes:
When we have a bad default--and I'd argue that for anyone not
developing PostgreSQL itself, showing system functions is a bad
default--we should change it to something sane.
I disagree with your parenthetical argument here, mainly on the strength
of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/04/2008, Tom Lane wrote:
David Fetter writes:
When we have a bad default--and I'd argue that for anyone not
developing PostgreSQL itself, showing system functions is a bad
default--we should change it to something sane.
I disagree
Pavel Stehule [EMAIL PROTECTED] writes:
I actualized sql/psm patch. This patch can be downloaded from
http://www.pgsql.cz/patches/plpgpsm.diff.gz
The fundamental problem I've got with this patch is that it adds 400K
of new code (and that's just the code, not counting documentation or
regression
On Tue, 2008-04-01 at 15:34 +, [EMAIL PROTECTED] wrote:
I would really prefer a more loosely coupled system.
The functionality will be much the same. The implementation would be
more difficult and obscure and there would be more points of failure and
more things to configure, but it wouldn't
Brendan Jurd [EMAIL PROTECTED] writes:
If I read Greg's latter proposal correctly, he was suggesting
\df Lists all user functions
\df [pattern] Lists both system and user functions matching [pattern]
\df * Lists all system and user functions
Hmm, I must've misread it, because I didn't
Tom Lane wrote:
One question: should \df really list *all* nonsystem functions? Or just
the ones that are visible in your search path? I'd be inclined to say
the second.
+1 (although maybe that discussion belongs on -hackers, or even -general)
cheers
andrew
--
Sent via
Tom Lane [EMAIL PROTECTED] writes:
Brendan Jurd [EMAIL PROTECTED] writes:
If I read Greg's latter proposal correctly, he was suggesting
\df Lists all user functions
\df [pattern] Lists both system and user functions matching [pattern]
\df * Lists all system and user functions
Hmm, I
FYI, the patch author and survey requestor has withdrawn the patch with
the following comment:
I think we can reject this patch. I don't process yet output from survey
on general, but it seems that more users prefer pg_ prefix, but idea of
pgc command seems to be better. I think it is good
Hello
On 01/04/2008, Tom Lane [EMAIL PROTECTED] wrote:
Pavel Stehule [EMAIL PROTECTED] writes:
I actualized sql/psm patch. This patch can be downloaded from
http://www.pgsql.cz/patches/plpgpsm.diff.gz
The fundamental problem I've got with this patch is that it adds 400K
of new code
22 matches
Mail list logo
