[HACKERS] Tuple alignment

2007-06-17 Thread Heikki Linnakangas
Why do we require that t_hoff is MAXALIGNed? ISTM that if the first field in a tuple doesn't require alignment, it could be stored immediately after the null bitmap, without padding. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---(end of broadca

Re: [HACKERS] Bugtraq: Having Fun With PostgreSQL

2007-06-17 Thread Magnus Hagander
> >> That won't help; that would introduce the "embarrassment" of having a > >> known default password. > > > No it wouldn't unless the packagers set it up to do that. My point is > > that when a packager (or source) runs initdb, it would prompt for the > > postgres user password. > > Practical

Re: [HACKERS] Bugtraq: Having Fun With PostgreSQL

2007-06-17 Thread Tom Lane
"Joshua D. Drake" <[EMAIL PROTECTED]> writes: > Christopher Browne wrote: >> That won't help; that would introduce the "embarrassment" of having a >> known default password. > No it wouldn't unless the packagers set it up to do that. My point is > that when a packager (or source) runs initdb, it

Re: [HACKERS] Load Distributed Checkpoints, revised patch

2007-06-17 Thread ITAGAKI Takahiro
Heikki Linnakangas <[EMAIL PROTECTED]> wrote: > Michael Paesold wrote: > > Why do you think so? Is it too much risk to adapt the sorted writes? The > > numbers shown by ITAGAKI Takahiro looked quite impressive, at least for > > large shared_buffers configurations. The reactions where rather > >

Re: [HACKERS] Bugtraq: Having Fun With PostgreSQL

2007-06-17 Thread Tom Lane
Christopher Browne <[EMAIL PROTECTED]> writes: > The world rejoiced as [EMAIL PROTECTED] ("Joshua D. Drake") wrote: >> On #1, the fact that we allow trust as default is embarrassing. > This is a case where it takes careful thought to grasp whether there > is a problem or not. > If all we do is to

Re: [HACKERS] Bugtraq: Having Fun With PostgreSQL

2007-06-17 Thread Joshua D. Drake
Christopher Browne wrote: The world rejoiced as [EMAIL PROTECTED] ("Joshua D. Drake") wrote: Tom Lane wrote: We've debated #1 before, and a lot of repackagers change it, but I don't really feel a strong urge to change it in the source distro. As for #2, that's not a bug, it's intended behavio

Re: [HACKERS] Bugtraq: Having Fun With PostgreSQL

2007-06-17 Thread Christopher Browne
The world rejoiced as [EMAIL PROTECTED] ("Joshua D. Drake") wrote: > Tom Lane wrote: >> Michael Fuhr <[EMAIL PROTECTED]> writes: >>> A message entitled "Having Fun With PostgreSQL" was posted to Bugtraq >>> today. I haven't read through the paper yet so I don't know if the >>> author discusses sec

Re: [HACKERS] Bugtraq: Having Fun With PostgreSQL

2007-06-17 Thread Joshua D. Drake
Tom Lane wrote: Michael Fuhr <[EMAIL PROTECTED]> writes: A message entitled "Having Fun With PostgreSQL" was posted to Bugtraq today. I haven't read through the paper yet so I don't know if the author discusses security problems that need attention or if the article is more like a compilation o

Re: [HACKERS] CSVlog vs tabs

2007-06-17 Thread Andrew Dunstan
FAST PostgreSQL wrote: Andrew Dunstan wrote: Now that we've fixed the partial/interleaved log line issue, I have returned to trying toi get the CSV log patch into shape. Sadly, it still needs lots of work, even after Greg Smith and I both attacked it, so I am now going through it with a f

Re: [HACKERS] CSVlog vs tabs

2007-06-17 Thread FAST PostgreSQL
Andrew Dunstan wrote: Now that we've fixed the partial/interleaved log line issue, I have returned to trying toi get the CSV log patch into shape. Sadly, it still needs lots of work, even after Greg Smith and I both attacked it, so I am now going through it with a fine tooth comb. One issu

Re: [HACKERS] wrong sql statement crashes backend

2007-06-17 Thread Jaime Casanova
On 6/17/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote: Pavel Stehule wrote: >> >> Please don't send HTML-only email :-( > > I am sorry. It's stupid web mail. I didn't know so my messages was in > html format. > > Actually, it looks to me like it was sent as plain text encoded as base64. I got:

Re: [HACKERS] wrong sql statement crashes backend

2007-06-17 Thread Andrew Dunstan
Pavel Stehule wrote: Please don't send HTML-only email :-( I am sorry. It's stupid web mail. I didn't know so my messages was in html format. Actually, it looks to me like it was sent as plain text encoded as base64. I got: Content-Type: text/plain; charset=UTF-8; format=flowed Conten

Re: [HACKERS] wrong sql statement crashes backend

2007-06-17 Thread Pavel Stehule
Please don't send HTML-only email :-( I am sorry. It's stupid web mail. I didn't know so my messages was in html format. Anyway, seems I broke this a couple months ago. Fixed, thanks for the report. regards, tom lane ---(end of broadcast)-

Re: [HACKERS] wrong sql statement crashes backend

2007-06-17 Thread Tom Lane
"Pavel Stehule" <[EMAIL PROTECTED]> writes: > SGVsbG8KCkkgZm91bmQgc2ltcGx5IGZ1bmN0aW9uIHdoaWNoIGlzIGJ1Z2d5 > LCBidXQgaXQgY3Jhc2hlcyBzZXJ2ZXIKCkNSRUFURSBPUiBSRVBMQUNFIEZV > TkNUSU9OIHRlc3QoYW55YXJyYXkpClJFVFVSTlMgYW55YXJyYXkgQVMgJCQK > ICBTRUxFQ1QgJDFba107IC0tIGsgaXMgYnVnCiQkIExBTkdVQUdFIHNxbDsK > .

Re: [HACKERS] Updated tsearch documentation

2007-06-17 Thread Oleg Bartunov
On Sun, 17 Jun 2007, Bruce Momjian wrote: I have completed my first pass over the tsearch documentation: http://momjian.us/expire/fulltext/HTML/sql.html They are from section 14 and following. I have come up with a number of questions that I placed in SGML comments in these files:

[HACKERS] wrong sql statement crashes backend

2007-06-17 Thread Pavel Stehule
Hello I found simply function which is buggy, but it crashes server CREATE OR REPLACE FUNCTION test(anyarray) RETURNS anyarray AS $$ SELECT $1[k]; -- k is bug $$ LANGUAGE sql; SELECT test(array[10,2,3]); Correct function works well. Regards Pavel Stehule Output: postgres=# select version();