[BUGS] why "alter table" to change owner of sequence?

2007-12-10 Thread hubert depesz lubaczewski
if i create sequence m and then want to change it's owner to some other account i have to issue: alter table owner to ...; why can't it be: alter sequence? example: # create sequence x; CREATE SEQUENCE # \d List of relations Schema | Name | Type | Owner +--+--

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

2007-12-10 Thread Gregory Stark
"Adriaan van Os" <[EMAIL PROTECTED]> writes: > 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

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

2007-12-10 Thread hubert depesz lubaczewski
On Sun, Dec 09, 2007 at 03:32:17PM +, Simon Riggs wrote: > ALTER SEQUENCE blah INCREMENT BY val; this has the sideeffect that all concurrent nextvals() will also increment by val, which is not always acceptable. depesz -- quicksil1er: "postgres is excellent, but like any DB it requires a hi

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

2007-12-10 Thread NikhilS
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: [BUGS] BUG #3811: Getting multiple values from a sequence generator

2007-12-10 Thread Simon Riggs
On Mon, 2007-12-10 at 12:31 +0100, hubert depesz lubaczewski wrote: > On Sun, Dec 09, 2007 at 03:32:17PM +, Simon Riggs wrote: > > ALTER SEQUENCE blah INCREMENT BY val; > > this has the sideeffect that all concurrent nextvals() will also > increment by val, which is not always acceptable. So

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

2007-12-10 Thread Gregory Stark
"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

2007-12-10 Thread Alvaro Herrera
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] [BUGS] BUG #3799: csvlog skips some logs

2007-12-10 Thread Andrew Dunstan
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] [BUGS] BUG #3799: csvlog skips some logs

2007-12-10 Thread Alvaro Herrera
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

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

2007-12-10 Thread Alvaro Herrera
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

2007-12-10 Thread Tom Lane
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

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

2007-12-10 Thread Alvaro Herrera
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

[BUGS] BUG #3812: Delphi TADOStored procedure truncates time portion of the ftDateTime parameter using ODBC

2007-12-10 Thread A. Ozen Akyurek
The following bug has been logged online: Bug reference: 3812 Logged by: A. Ozen Akyurek Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2 Operating system: Windows XP Description:Delphi TADOStored procedure truncates time portion of the ftDateTime parameter us

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

2007-12-10 Thread Tom Lane
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.