Re: [HACKERS] Problem of a server gettext message.

From: "Tom Lane" <[EMAIL PROTECTED]> Are you sure about that? Why would gettext be converting to SJIS, when SJIS is nowhere in the environment it can see? I believe that Peter's hypothesis is that gettext is leaving the string in EUC_JP because it sees locale = C and so has no basis for doing

Re: [HACKERS] Release Note Changes

On Dec 10, 2007 6:43 PM, Andrew Dunstan <[EMAIL PROTECTED]> wrote: > > > Pavan Deolasee wrote: > > > > > > > > > > > > I don't agree completely. HOT updates is just one significant benefit of > > HOT and is constrained by the non-index column updates. But the other > > major benefit of truncating

Re: [HACKERS] Problem of a server gettext message.

"Hiroshi Saito" <[EMAIL PROTECTED]> writes: > Probably no. > GetText is conversion po(EUC_JP) to SJIS. Then, The stderr output of a server > is > outputted without an error to log by it. That's right message with it similar > to start-up. > However, The conversion obstacle of a message is encoun

Re: [HACKERS] Problem of a server gettext message.

Hi Peter-san. Thank you for various. ! - Original Message - From: "Peter Eisentraut" <[EMAIL PROTECTED]> Am Montag, 10. Dezember 2007 schrieb Hiroshi Saito: Hi. From: "Peter Eisentraut" <[EMAIL PROTECTED]> > Am Montag, 10. Dezember 2007 schrieb Hiroshi Saito: >> Hi Peter-san. >>

Re: [HACKERS] whats the deal with -u ?

On Monday 10 December 2007 10:16, Tom Lane wrote: > Further down the road, those whose notion of "intuitive" was formed > by mysql might lobby to have -u become an alternate spelling for -U, crontab, truss, sudo, ps, strace, top, etc... -- Robert Treat Build A Brighter LAMP :: Linux Apache {mid

Re: [HACKERS] Release Note Changes

Bruce Momjian wrote: Ah, glad you asked. It is now in the release note introduction that I added as part of this discussion: http://momjian.us/main/writings/pgsql/sgml/release-introduction.html I realize it wasn't documented but the issue was always open for discussion, as you have see

Re: [HACKERS] Release Note Changes

Joshua D. Drake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mon, 10 Dec 2007 18:40:52 -0500 (EST) > Bruce Momjian <[EMAIL PROTECTED]> wrote: > > > By trying to make one developer happy I have made two unhappy. > > I have removed Stefan Kaltenbrunner's name from that item. > >

Re: [HACKERS] whats the deal with -u ?

Stephen Frost <[EMAIL PROTECTED]> writes: > * Tom Lane ([EMAIL PROTECTED]) wrote: >> However, I think we should either get rid of -u or find a way to >> un-deprecate it. Right now, it's undocumented and as far as I can see >> the main effect of having it is to cause confusion such as that which >>

Re: [HACKERS] PGparam proposal

Andrew Chernow <[EMAIL PROTECTED]> writes: > This proposal extends libpq by adding a printf style functions for > sending and recveiving through the paramterized interface. I think a printf-style API is fundamentally a bad idea in this context. printf only works well when the set of concepts (data

Re: [HACKERS] Release Note Changes

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 > PostgreSQL two for the price of one. Postgre *and* SQL? :) - -- Greg Sabino Mullane [EMAIL PROTECTED] The first Postgres "Greg" (3 and counting now...) PGP Key: 0x14964AC8 200712101856 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC

Re: [HACKERS] Release Note Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Dec 2007 18:40:52 -0500 (EST) Bruce Momjian <[EMAIL PROTECTED]> wrote: > By trying to make one developer happy I have made two unhappy. > I have remved Stefan Kaltenbrunner's name from that item. > > Basically I should have expected this b

Re: [HACKERS] Release Note Changes

Tom Lane wrote: > Oleg Bartunov <[EMAIL PROTECTED]> writes: > > On Mon, 10 Dec 2007, Bruce Momjian wrote: > >> That is an excellent suggestion, done: > >> > >> Full text search is integrated into the core database > >> system (Teodor, Oleg, Stefan Kaltenbrunner) > > > Wait, I think we need more w

Re: [HACKERS] Release Note Changes

Release note introduction attached and applied. --- bruce wrote: > Based on this discussion I think it is clear the release notes chapter > needs an introductory section. This would not be for any specific > release but the

[HACKERS] PGparam proposal

We will have a 0.6 patch tomorrow. This is not a patch, its a proposal. The implementation has been adjusted and is now a simple printf-style interface. This is just a design proposal to see if people like the idea and interface. Up to this point, we have not provided a formal proposal; ju

Re: [HACKERS] [BUGS] BUG #3799: csvlog skips some logs

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Another change I did was to change a "%.*s" to "%*s". The "precision" > marker seems useless AFAICT. This is wrong, broken, will cause crashes on platforms where the PS string is not null-terminated. (Hint: .* is a maximum width, * is a minimum width.

Re: [HACKERS] Release Note Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Dec 2007 17:56:01 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: > Oleg Bartunov <[EMAIL PROTECTED]> writes: > > On Mon, 10 Dec 2007, Bruce Momjian wrote: > >> That is an excellent suggestion, done: > >> > >> Full text search is integrated into

Re: [HACKERS] Release Note Changes

Oleg Bartunov <[EMAIL PROTECTED]> writes: > On Mon, 10 Dec 2007, Bruce Momjian wrote: >> That is an excellent suggestion, done: >> >> Full text search is integrated into the core database >> system (Teodor, Oleg, Stefan Kaltenbrunner) > Wait, I think we need more words about original authors ! I

Re: [HACKERS] Release Note Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Dec 2007 17:26:11 -0500 (EST) Bruce Momjian <[EMAIL PROTECTED]> wrote: > > Tom and you disagreed. I understand the reasoning and I don't > > actually disagree with the thought process but I think the thought > > process is flawed. I do not

Re: [HACKERS] Release Note Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Dec 2007 17:16:12 -0500 (EST) Bruce Momjian <[EMAIL PROTECTED]> wrote: > Kris Jurka wrote: > > > > > > On Mon, 10 Dec 2007, Joshua D. Drake wrote: > > > > > 3. It was grunt work that should have been done with the original > > > patch th

Re: [HACKERS] Release Note Changes

On Mon, 10 Dec 2007, Bruce Momjian wrote: Kris Jurka wrote: On Mon, 10 Dec 2007, Joshua D. Drake wrote: 3. It was grunt work that should have been done with the original patch that didn't get done. Stefan picked up the ball and ran with it and produced something that will make our product m

Re: [HACKERS] Release Note Changes

Joshua D. Drake wrote: > Bruce Momjian wrote: > > Joshua D. Drake wrote: > >> Bruce Momjian wrote: > >>> Joshua D. Drake wrote: > I assumed the white paper would have proper attribution. > >>> Right, but is the white paper going to be thorough to mention _all_ > >>> changes? > >>> > >> Hmmm go

Re: [HACKERS] Release Note Changes

Alvaro Herrera wrote: > Alvaro Herrera wrote: > > Joshua D. Drake wrote: > > > > > We even have two Gavins. However I think we will truly reach the point > > > of no return with we have two Heikkis. Once we have two Heikkis it will > > > be obvious to anyone that we are the World's most globally d

Re: [HACKERS] Release Note Changes

Kris Jurka wrote: > > > On Mon, 10 Dec 2007, Joshua D. Drake wrote: > > > 3. It was grunt work that should have been done with the original patch > > that didn't get done. Stefan picked up the ball and ran with it and > > produced something that will make our product more usable for the end >

Re: [HACKERS] Problem of a server gettext message.

Peter Eisentraut <[EMAIL PROTECTED]> writes: > When the server wants to send an error message to the client, it will > convert them from the server to the client encoding. The English > messages are ASCII, so this will work, because server encodings are > required to be ASCII compatible. The resu

Re: [HACKERS] archive_command failures report confusing exit status

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Peter Eisentraut wrote: >> I figured it would make sense if pgarch.c used the same mechanism that >> postmaster.c uses to report the various variants of regular and signal >> exits. > Hmm. Getting rid of the "(PID 0)" is going to be a mess enough for >

Re: [HACKERS] Release Note Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Dec 2007 18:13:58 -0300 Alvaro Herrera <[EMAIL PROTECTED]> wrote: > Alvaro Herrera wrote: > > Joshua D. Drake wrote: > > > > > We even have two Gavins. However I think we will truly reach the > > > point of no return with we have two Heikk

Re: [HACKERS] Release Note Changes

Alvaro Herrera wrote: > Joshua D. Drake wrote: > > > We even have two Gavins. However I think we will truly reach the point > > of no return with we have two Heikkis. Once we have two Heikkis it will > > be obvious to anyone that we are the World's most globally developed > > advanced Open Source

Re: [HACKERS] archive_command failures report confusing exit status

On Mon, 2007-12-10 at 18:27 +0100, Peter Eisentraut wrote: > Failures of archive_command calls report a confusing exit status such as: > > LOG: archive command "cp 'pg_xlog/0001' > '/nonexistent/0001'" failed: return code 256 > > The actual return code is

Re: [HACKERS] Release Note Changes

Gregory Stark wrote: > "Tom Lane" <[EMAIL PROTECTED]> writes: > >> When Tom Lockhart was around the project it was even messier, since he and I >> shared not only the same first name but all three initials. > > Then there's Greg Stark, Greg Smith, and Greg Sabino (Mullane). > > Perhaps we should

[HACKERS] Trigger proglem

Good day, We have written a trigger that is We have written a trigger that is associated with the table. When any changes are submitted, then this trigger reconstruct and writes sql query to the table querieslog. We have found a problem: from time to time some sql query is not written while the q

Re: [HACKERS] archive_command failures report confusing exit status

Peter Eisentraut wrote: > I figured it would make sense if pgarch.c used the same mechanism that > postmaster.c uses to report the various variants of regular and signal > exits. Hmm. Getting rid of the "(PID 0)" is going to be a mess enough for translations that I think it is worth pgarch.c hav

Re: [HACKERS] Problem of a server gettext message.

Am Montag, 10. Dezember 2007 schrieb Hiroshi Saito: > Hi. > > From: "Peter Eisentraut" <[EMAIL PROTECTED]> > > > Am Montag, 10. Dezember 2007 schrieb Hiroshi Saito: > >> Hi Peter-san. > >> > >> It is this. > >> http://winpg.jp/~saito/pg83/ja.zip > > > > Sorry, we need the *po* (text) files, not the

Re: [HACKERS] Release Note Changes

Joshua D. Drake wrote: > We even have two Gavins. However I think we will truly reach the point > of no return with we have two Heikkis. Once we have two Heikkis it will > be obvious to anyone that we are the World's most globally developed > advanced Open Source database. Hey, we have two Hirosh

Re: [HACKERS] Release Note Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Dec 2007 16:12:54 + Gregory Stark <[EMAIL PROTECTED]> wrote: > > "Tom Lane" <[EMAIL PROTECTED]> writes: > > > When Tom Lockhart was around the project it was even messier, since > > he and I shared not only the same first name but all

Re: [HACKERS] Release Note Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Dec 2007 12:14:58 -0500 (EST) Kris Jurka <[EMAIL PROTECTED]> wrote: > > > On Mon, 10 Dec 2007, Joshua D. Drake wrote: > > > 3. It was grunt work that should have been done with the original > > patch that didn't get done. Stefan picked u

[HACKERS] archive_command failures report confusing exit status

Failures of archive_command calls report a confusing exit status such as: LOG: archive command "cp 'pg_xlog/0001' '/nonexistent/0001'" failed: return code 256 The actual return code is 1; it neglects to apply WEXITSTATUS(). I figured it would make sense

Re: [HACKERS] Problem of a server gettext message.

Hi. From: "Peter Eisentraut" <[EMAIL PROTECTED]> Am Montag, 10. Dezember 2007 schrieb Hiroshi Saito: Hi Peter-san. It is this. http://winpg.jp/~saito/pg83/ja.zip Sorry, we need the *po* (text) files, not the *mo* (binary) files. Ooops, Although it is an object for Version 8.2.5. http://w

Re: [HACKERS] Release Note Changes

On Mon, 10 Dec 2007, Joshua D. Drake wrote: 3. It was grunt work that should have been done with the original patch that didn't get done. Stefan picked up the ball and ran with it and produced something that will make our product more usable for the end user. Then why not list Stefan as a

Re: [HACKERS] Problem of a server gettext message.

Am Montag, 10. Dezember 2007 schrieb Hiroshi Saito: > Hi Peter-san. > > It is this. > http://winpg.jp/~saito/pg83/ja.zip Sorry, we need the *po* (text) files, not the *mo* (binary) files. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--

Re: [HACKERS] O(n^2) aggregates

Hello > > select count(*) > from huge > where h = any ((select arrayize( (1+random()*3)::integer ) > from generate_series(1,1000) > )::integer[]) > select array(select (1+random()*3):: integer from generate_series(1,4)); Time: 111,807 ms -

Re: [HACKERS] Release Note Changes

Andrew Dunstan wrote: Yeah, laziness on the part of those preparing the release notes is certainly a factor ;-). Anyway, maybe a policy of "drop the last name on second and later mentions, unless this might cause confusion" would work. You've probably written more in this thr

Re: [HACKERS] Release Note Changes

Bruce Momjian wrote: Joshua D. Drake wrote: Bruce Momjian wrote: Joshua D. Drake wrote: I assumed the white paper would have proper attribution. Right, but is the white paper going to be thorough to mention _all_ changes? Hmmm good question which gets back to where we started :). My very fir

Re: [HACKERS] pg_dump roles support

* Tom Lane ([EMAIL PROTECTED]) wrote: > Stephen Frost <[EMAIL PROTECTED]> writes: > > Far as I can tell anyway. What would you suggest? The point here is > > that joesysadmin shouldn't get full postgres privs on login since most > > of the time he won't need them. > > It's sane to set up a manua

Re: [HACKERS] pg_dump roles support

Stephen Frost <[EMAIL PROTECTED]> writes: > * Tom Lane ([EMAIL PROTECTED]) wrote: >> Seems like the correct answer to that is "use a saner role >> configuration". > Far as I can tell anyway. What would you suggest? The point here is > that joesysadmin shouldn't get full postgres privs on login s

Re: [HACKERS] Problem of a server gettext message.

Hi Peter-san. It is this. http://winpg.jp/~saito/pg83/ja.zip Regards, Hiroshi Saito - Original Message - From: "Peter Eisentraut" <[EMAIL PROTECTED]> Am Montag, 10. Dezember 2007 schrieb Hiroshi Saito: 2. Japanese local message of po file to setting(share/locale/ja) . Could we s

Re: [HACKERS] pg_dump roles support

* Tom Lane ([EMAIL PROTECTED]) wrote: > Stephen Frost <[EMAIL PROTECTED]> writes: > > create role admin with noinherit; > > grant postgres to admin; > > grant admin to joesysadmin; > > > pg_dump -U joesysadmin mydb; > > > Fails because joesysadmin hasn't got rights to everything directl

Re: [HACKERS] Problem of a server gettext message.

Am Montag, 10. Dezember 2007 schrieb Hiroshi Saito: > 2. Japanese local message of po file to setting(share/locale/ja) . Could we see the contents of this file? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)---

Re: [HACKERS] pg_dump roles support

Stephen Frost <[EMAIL PROTECTED]> writes: > create role admin with noinherit; > grant postgres to admin; > grant admin to joesysadmin; > pg_dump -U joesysadmin mydb; > Fails because joesysadmin hasn't got rights to everything directly. Seems like the correct answer to that is "use a sa

Re: [HACKERS] Release Note Changes

"Tom Lane" <[EMAIL PROTECTED]> writes: > When Tom Lockhart was around the project it was even messier, since he and I > shared not only the same first name but all three initials. Then there's Greg Stark, Greg Smith, and Greg Sabino (Mullane). Perhaps we should just go by uid. -- Gregory St

Re: [HACKERS] Release Note Changes

Tom Lane wrote: Heikki Linnakangas <[EMAIL PROTECTED]> writes: Dave Page wrote: That's inaccurate - I've been listed by full name for at least the last 3 or 4 releases. I realise I'm not the biggest contributor to the core code, but 'newer' certainly isn't right. Maybe

[HACKERS] pg_dump roles support

Greetings, Discussing psql options made me recall an annoying problem that we've run into. There's no way (unless it was added to 8.3 and I missed it, but I don't think so) to tell pg_dump 'switch to this role before doing anything else'. That's very frustrating when you use no-inherit

Re: [HACKERS] Release Note Changes

Heikki Linnakangas <[EMAIL PROTECTED]> writes: > Dave Page wrote: >> That's inaccurate - I've been listed by full name for at least the last 3 or >> 4 releases. I realise I'm not the biggest contributor to the core code, but >> 'newer' certainly isn't right. > Maybe that's because you have such

Re: [HACKERS] whats the deal with -u ?

* Tom Lane ([EMAIL PROTECTED]) wrote: > However, I think we should either get rid of -u or find a way to > un-deprecate it. Right now, it's undocumented and as far as I can see > the main effect of having it is to cause confusion such as that which > started this thread. > > On the whole I'm in f

Re: [HACKERS] [BUGS] BUG #3799: csvlog skips some logs

Tom Lane wrote: > Andrew Dunstan <[EMAIL PROTECTED]> writes: > > If it's about what to quote, we need to quote anything that might > > contain a newline, quote or comma. Filenames certainly come into that > > category. > > These are not general file paths, these are base names of our own C > sourc

Re: [HACKERS] O(n^2) aggregates

Gregory Stark <[EMAIL PROTECTED]> writes: > The solution to this would analogous to what we did to count(). We would need > to add a field to ArrayMetaState which is stored in fn_extra to remember the > last array returned. Then if array_push notices it has been called from an > aggregate context i

Re: [HACKERS] [BUGS] BUG #3799: csvlog skips some logs

Andrew Dunstan <[EMAIL PROTECTED]> writes: > If it's about what to quote, we need to quote anything that might > contain a newline, quote or comma. Filenames certainly come into that > category. These are not general file paths, these are base names of our own C source code files. I don't have a

[HACKERS] Problem of a server gettext message.

Hi. I think this has many problems. However, by the reason the release is approaching, this is not the situation which I'm looking at leisurely.. Server message has a problem by 8.3beta4 on windows. The situation is this. 1. initdb -E UTF-8 --no-locale This is C locale. http://winpg.jp/~

Re: [HACKERS] whats the deal with -u ?

Stephen Frost <[EMAIL PROTECTED]> writes: > * Peter Eisentraut ([EMAIL PROTECTED]) wrote: >> So as far as I can tell, the available options -U and -W serve all the >> existing use cases. I would have no issue with getting rid of the -W option >> if someone wants to take responsibility for ensurin

Re: [HACKERS] [BUGS] BUG #3799: csvlog skips some logs

Alvaro Herrera wrote: > Andrew Dunstan wrote: > > > Not sure I understand what this comment I noticed on a very brief glance is > > about: > > > > /* assume no newlines in funcname or filename... */ > > > > If it's about what to quote, we need to quote anything that might contain a > > newline,

Re: [HACKERS] [BUGS] BUG #3799: csvlog skips some logs

Andrew Dunstan wrote: > Not sure I understand what this comment I noticed on a very brief glance is > about: > > /* assume no newlines in funcname or filename... */ > > If it's about what to quote, we need to quote anything that might contain a > newline, quote or comma. Filenames certainly com

[HACKERS] O(n^2) aggregates

I was trying to test my patch to do posix_fadvise to speed up bitmap heap scans (with disappointing results so far) and ran into a bit of a gotcha. I'm not sure where this should be documented but it probably should be somewhere. In order to test bitmap heap scan I had to build an array and use t

Re: [HACKERS] [BUGS] BUG #3799: csvlog skips some logs

Alvaro Herrera wrote: Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> writes: Tom Lane wrote: Well, if we want to cram all that stuff in there, how shall we do it? It seems wrong to put all those lines into one text field, but I'm not sure I want to add six more text fields

Re: [HACKERS] whats the deal with -u ?

* Peter Eisentraut ([EMAIL PROTECTED]) wrote: > So as far as I can tell, the available options -U and -W serve all the > existing use cases. I would have no issue with getting rid of the -W option > if someone wants to take responsibility for ensuring that it will really > never be necessary.

Re: [HACKERS] Release Note Changes

Le lundi 10 décembre 2007, Bruce Momjian a écrit : > > http://repo.or.cz/w/PostgreSQL.git > > http://repo.or.cz/w/PostgreSQL.git?a=shortlog;h=master > > http://repo.or.cz/w/PostgreSQL.git?a=shortlog;h=REL8_2_STABLE > > I like the branch option but I don't like the title being duplicated as >

Re: [HACKERS] [BUGS] BUG #3811: Getting multiple values from a sequence generator

"NikhilS" <[EMAIL PROTECTED]> writes: > Coincidently, I very briefly discussed (offline) about supporting > expressions while doing loads using COPY FROM with Heikki a while back. From > the above mail exchanges, it does appear that adding this kind of > functionality will be useful while doing bu

Re: [HACKERS] [BUGS] BUG #3799: csvlog skips some logs

Tom Lane wrote: > Andrew Dunstan <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> Well, if we want to cram all that stuff in there, how shall we do it? > >> It seems wrong to put all those lines into one text field, but I'm > >> not sure I want to add six more text fields to the CSV format > >>

Re: [HACKERS] Release Note Changes

Pavan Deolasee wrote: On Dec 8, 2007 3:42 AM, Andrew Dunstan <[EMAIL PROTECTED] > wrote: Bruce Momjian wrote: > Andrew Dunstan wrote: > I still think this needs to be qualified either way. As it stands it's quite misleading. Man

Re: [HACKERS] PGparam timestamp question

>>Or was the code incorrectly used? Hard for me to say, but I think its about caller context. The way I am using it might be different ... hey the function was static ... copy & paster be warned! The code appears to be doing the same thing as the backend (with the exclusion of backend stuff l

Re: [HACKERS] Release Note Changes

Bruce Momjian wrote: > Dave Page wrote: >> David != Dave > > Yea, but that is so subtle that is seems too error-prone. I think you missed the smiley. It doesn't bother me if I'm named in full or not, just that the introduction is accurate - which you've already fixed. /D ---

Re: [HACKERS] Release Note Changes

Dave Page wrote: > Bruce Momjian wrote: > > Heikki Linnakangas wrote: > >> Dave Page wrote: > First-name-only > entries represent established developers, while full names represent > newer contributors. > >>> That's inaccurate - I've been listed by full name for at least the last

Re: [HACKERS] Release Note Changes

Bruce Momjian wrote: > Heikki Linnakangas wrote: >> Dave Page wrote: First-name-only entries represent established developers, while full names represent newer contributors. >>> That's inaccurate - I've been listed by full name for at least the last 3 >>> or 4 releases. I rea

Re: [HACKERS] Release Note Changes

Joshua D. Drake wrote: > Bruce Momjian wrote: > > Joshua D. Drake wrote: > > >> I assumed the white paper would have proper attribution. > > > > Right, but is the white paper going to be thorough to mention _all_ > > changes? > > > > Hmmm good question which gets back to where we started :). My

Re: [HACKERS] Release Note Changes

Heikki Linnakangas wrote: > Dave Page wrote: > >> First-name-only > >>entries represent established developers, while full names represent > >>newer contributors. > > > > That's inaccurate - I've been listed by full name for at least the last 3 > > or 4 releases. I realise I'm not the bi

Re: [HACKERS] Release Note Changes

Dimitri Fontaine wrote: -- Start of PGP signed section. > Hi, > > Le lundi 10 d?cembre 2007, Bruce Momjian a ?crit?: > > Based on this discussion I think it is clear the release notes chapter > > needs an introductory section. This would not be for any specific > > release but the release notes i

Re: [HACKERS] Release Note Changes

Brendan Jurd wrote: > On Dec 10, 2007 10:39 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote: > > I like the realease notes intro. You may have already picked up on > these, but a couple typos: > > > A names appearing next to an item represents the major developer for > > that item.

Re: [HACKERS] [BUGS] BUG #3811: Getting multiple values from a sequence generator

Hi, > > Right, I want to use it with a bulk operation, say importing a million > records > > with COPY. Calling nextval one million times looks to me like an > enormous waste > > of resources. Suppose, you are on an ADSL line: it will cost one million > times > > the ping time of the ADSL line (sa

Re: [HACKERS] whats the deal with -u ?

Am Montag, 10. Dezember 2007 schrieb Tom Lane: > "Joshua D. Drake" <[EMAIL PROTECTED]> writes: > > As I recall there was a bug under very specific circumstances that a > > password prompt would not appear. Thus we added the option for -W. > > I don't see any evidence for that theory in the CVS logs

Re: [HACKERS] Release Note Changes

Dave Page wrote: First-name-only entries represent established developers, while full names represent newer contributors. That's inaccurate - I've been listed by full name for at least the last 3 or 4 releases. I realise I'm not the biggest contributor to the core code, but '

Re: [HACKERS] Problem with ControlFileData structure being ABI depe ndent

Dave Page wrote: > Tom Lane wrote: >> Dave Page <[EMAIL PROTECTED]> writes: >>> Gregory Stark wrote: An alternative is leaving it in the project file but putting something like this in c.h: >> >> Put it in win32.h, please. c.h shouldn't get cluttered with >> platform-specific kluges

Re: [HACKERS] Release Note Changes

Hi, Le lundi 10 décembre 2007, Bruce Momjian a écrit : > Based on this discussion I think it is clear the release notes chapter > needs an introductory section. This would not be for any specific > release but the release notes in general. Excellent idea, IMHO. > I need help with the CVS sectio

Re: [HACKERS] PGparam timestamp question

On Sun, Dec 09, 2007 at 11:54:25AM -0500, Andrew Chernow wrote: > That explains why my libpq code was getting 3AM for "without time zone" > values. I am using code from src/interfaces/ecpg/pgtypeslib/timestamp.c > timestamp2tm(). That uses localtime() after converting the timestamp to an > epo