On Fri, Aug 20, 2004 at 11:44:28PM -0400, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Darcy Buskermolen wrote:
* remove to_char(interval) if we initdb or mention removal
I vote just to mention it's removal at this time,
Agreed. Done.
While I don't care that much one
On August 20, 2004 09:01 pm, Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Darcy Buskermolen wrote:
* remove to_char(interval) if we initdb or mention removal
I vote just to mention it's removal at this time,
Agreed. Done.
I don't see any
Bruce Momjian wrote
P O S T G R E S Q L
8 . 0 O P E NI T E M S
a few comments...
* add xid to log_line_prefix for PITR
This at first sounded like a wonderfully simple solution, though on
consideration, I'm not sure I'd
Tom Lane wrote:
Okay, I don't want to force an initdb just for this either. But if we
do one for other reasons, it's toast.
I don't see why an initdb is required: if we want to remove it, we can
replace the function's implementation with elog(ERROR, this function
has been removed), or the like.
Neil Conway [EMAIL PROTECTED] writes:
Tom Lane wrote:
Okay, I don't want to force an initdb just for this either. But if we
do one for other reasons, it's toast.
I don't see why an initdb is required: if we want to remove it, we can
replace the function's implementation with elog(ERROR,
Tom Lane wrote:
Neil Conway [EMAIL PROTECTED] writes:
Tom Lane wrote:
Okay, I don't want to force an initdb just for this either. But if we
do one for other reasons, it's toast.
I don't see why an initdb is required: if we want to remove it, we can
replace the function's
On Sat, 2004-08-21 at 11:26, Bruce Momjian wrote:
Tom Lane wrote:
snip
No, not at all. A nonfunctional catalog entry gets in the way of the
user replacing the function, should he wish to do that.
Yea, but I would call the odds of that pretty negligible.
What if they're trying to restore
P O S T G R E S Q L
8 . 0 O P E NI T E M S
Current version at ftp://momjian.postgresql.org/pub/postgresql/open_items.
Changes
---
* Win32
o add binary version stamps?
o fix signal-safe socket handler for SSL
On August 20, 2004 01:28 pm, Bruce Momjian wrote:
P O S T G R E S Q L
8 . 0 O P E NI T E M S
* determine proper crash recovery/logging for pg_subtrans
* remove to_char(interval) if we initdb or mention removal
I vote just to
Agreed. Done.
---
Darcy Buskermolen wrote:
On August 20, 2004 01:28 pm, Bruce Momjian wrote:
P O S T G R E S Q L
8 . 0 O P E NI T E M S
* determine
Bruce Momjian [EMAIL PROTECTED] writes:
Darcy Buskermolen wrote:
* remove to_char(interval) if we initdb or mention removal
I vote just to mention it's removal at this time,
Agreed. Done.
While I don't care that much one way or the other --- what is the
difference between this and the
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Darcy Buskermolen wrote:
* remove to_char(interval) if we initdb or mention removal
I vote just to mention it's removal at this time,
Agreed. Done.
While I don't care that much one way or the other --- what is the
Bruce Momjian [EMAIL PROTECTED] writes:
I see it in the SGML docs:
Warning: literalfunctionto_char/function(typeinterval/type,
typetext/type)/literal
is deprecated and should not be used in newly-written code. It will be removed
in the next version.
I suppose that is enough
13 matches
Mail list logo
