"Ed L." <[EMAIL PROTECTED]> writes:
> I have a 5-line check-last-filename patch, but it's so small you probably
> just want to add it yourself?
Yeah, it's pretty trivial. I just applied the attached.
regards, tom lane
Index: syslogger.c
On Monday September 20 2004 6:02, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> >> That might work for you, but it's not portable.
> >
> > Do you consider pg_tm.tm_gmtoff reliable and portable from
> > pg_localtime(&now)?
>
> Yeah, in fact I was just adapting the patch to use that.
I hav
"Ed L." <[EMAIL PROTECTED]> writes:
>> That might work for you, but it's not portable.
> Do you consider pg_tm.tm_gmtoff reliable and portable from
> pg_localtime(&now)?
Yeah, in fact I was just adapting the patch to use that.
regards, tom lane
-
On Monday September 20 2004 5:45, Ed L. wrote:
> On Monday September 20 2004 5:39, Tom Lane wrote:
> > "Ed L." <[EMAIL PROTECTED]> writes:
> > > + /*
> > > + * We expect a strftime(%z) result of the form "[+-]HHMM"
> > > according to + * RFC822-conformant dates, where HH:MM is the
> >
On Monday September 20 2004 5:39, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > + /*
> > + * We expect a strftime(%z) result of the form "[+-]HHMM"
> > according to + * RFC822-conformant dates, where HH:MM is the
> > unsigned UTC offset. + * If we don't get it, just r
"Ed L." <[EMAIL PROTECTED]> writes:
> + /*
> + * We expect a strftime(%z) result of the form "[+-]HHMM" according to
> + * RFC822-conformant dates, where HH:MM is the unsigned UTC offset.
> + * If we don't get it, just return zero offset, and let the logs
> + * rotate on UT
On Monday September 20 2004 4:57, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > Consider the case if one is
> > truncating logs on rotation and rotating hourly. UTC vs local is
> > irrelevant. If local time shifts backward from 02:00 to 01:00, our UTC
> > offset will move in the negat
Greg Stark <[EMAIL PROTECTED]> writes:
> This patch allows subqueries without aliases. This is SQL-non-spec-compliant
> syntax that Oracle supports and many users expect to work.
AFAIR you're the first to propose that we ignore the SQL spec here.
When I wrote "see if anyone complains", I had in mi
"Ed L." <[EMAIL PROTECTED]> writes:
> Consider the case if one is
> truncating logs on rotation and rotating hourly. UTC vs local is
> irrelevant. If local time shifts backward from 02:00 to 01:00, our UTC
> offset will move in the negative direction. If 1) our policy were to
> truncate on r
On Monday September 20 2004 4:43, Ed L. wrote:
>
> This patch rotates logs on local time boundaries instead of UTC
> boundaries, e.g., midnight local for daily rotation instead of midnight
> UTC. It does so by parsing the "%z" result from strftime().
>
> ... I am arguing for
> inclusion of this p
On Monday August 30 2004 11:07, Ed L. wrote:
> On Monday August 30 2004 10:56, Tom Lane wrote:
> > "Ed L." <[EMAIL PROTECTED]> writes:
> > > Attached is a revised patch:
> >
> > Applied with minor revisions.
> >
> > > I did not add UTC offset logic nor logic to shift to top of the
> > > hour/day fo
T E Schmitz <[EMAIL PROTECTED]> writes:
> There's a German saying "Go and find a parking-meter", i.e. suggesting to pop a
> coin in the parking-meter and talk to it as nobody else wants to listen. ;-)
Yes well I anticipated such a response. So I tried my hand at it myself.
Well I finally found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Mon, 20 Sep 2004, Peter Eisentraut wrote:
http://www.gunduz.org/postgresql/translation/PostgreSQL-8.0/initdb-tr.po
This appears to be the binary ("MO") file. You need to send the source ("PO")
file.
Ok, got it.
http://www.gunduz.org/postgresql/t
Alvaro Herrera wrote:
On Sun, Sep 19, 2004 at 10:29:32AM +0200, LELARGE Guillaume wrote:
Sorry to reply to your post so late...
Peter Eisentraut wrote:
- Please actually encode the files in the declared encoding. The pg_ctl
translation was partially encoded in UTF-8. I did not install that
one.
Tom Lane wrote:
> > It is now fixed in the attached patch.
>
> Applied with some additional cleanup (the code wasn't multibyte-aware,
> and so could get fooled in some Far Eastern encodings).
I am very pleased to hear. This was my first patch submitted. :-)
Best Regards,
Michael Paesold
--
"Michael Paesold" <[EMAIL PROTECTED]> writes:
>> Per SQL spec, the backend thinks that /* .. */ nests:
> It is now fixed in the attached patch.
Applied with some additional cleanup (the code wasn't multibyte-aware,
and so could get fooled in some Far Eastern encodings).
> Concerning my other pat
Josh Berkus <[EMAIL PROTECTED]> writes:
> Re-building CVS I noticed that I never submitted this doc-only patch to
> postgresql.conf.sample.
Applied, with a little extra massaging of my own.
regards, tom lane
---(end of broadcast)--
On Sun, Sep 19, 2004 at 10:29:32AM +0200, LELARGE Guillaume wrote:
> Sorry to reply to your post so late...
>
> Peter Eisentraut wrote:
> > - Please actually encode the files in the declared encoding. The pg_ctl
> > translation was partially encoded in UTF-8. I did not install that
> > one.
>
>
Am Montag, 20. September 2004 09:27 schrieb Serguei Mokhov:
> Please use this for the backend translations when you
> get to install 'em. This one replaces the one sent earlier
> with more messages translated and fixed.
Done.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Am Sonntag, 19. September 2004 10:29 schrieb LELARGE Guillaume:
> You'll find two attachments for 7.4 and 7.5 messages.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: Have you searched our l
Am Mittwoch, 15. September 2004 18:42 schrieb Devrim GUNDUZ:
> http://www.gunduz.org/postgresql/translation/PostgreSQL-8.0/initdb-tr.po
This appears to be the binary ("MO") file. You need to send the source ("PO")
file. Compare:
$ file initdb-tr.po
initdb-tr.po: GNU message catalog (little end
Am Freitag, 17. September 2004 08:09 schrieb Zhenbang Wei:
> Update to latest messages and fix those invalid.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: Have you searched our list archiv
Michael Paesold wrote
> Tom Lane wrote:
> > Per SQL spec, the backend thinks that /* .. */ nests:
> >
> > regression=# /* some /* comment */ comment */ select 1;
> > ?column?
> > --
> > 1
> > (1 row)
> >
> > As it stands, is_transact_command will get confused by this.
It is now fi
Am Mittwoch, 15. September 2004 03:47 schrieb Alvaro Herrera:
> Attached are the backend's and pgscripts spanish translation updates.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: if postin
Am Mittwoch, 15. September 2004 00:49 schrieb Alvaro Herrera:
> Attached are pg_controldata and pg_resetxlog spanish translation
> updated.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 8: exp
Am Mittwoch, 15. September 2004 00:24 schrieb Alvaro Herrera:
> Attached are updated spanish translations for libpq and pg_dump.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: don't forget t
Am Dienstag, 14. September 2004 08:24 schrieb Serguei Mokhov:
> Sorry for pushing more translation updates on your head
> right away ;-) Please apply to 8.0. As of this email
> these all should be 100%...
Done.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
27 matches
Mail list logo
