"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> 2008/9/1 Tom Lane <[EMAIL PROTECTED]>:
>> However, since this is a behavioral change that could break code that
>> works now, I think it should be a HEAD-only change; no backpatch.
> I agree - it's could break only 100% wrong code, but it could problem
David Fetter <[EMAIL PROTECTED]> writes:
> On Tue, Sep 02, 2008 at 02:42:25AM -0400, Tom Lane wrote:
>> It's not like we haven't seen a SQL draft go down in flames before.
> Do you think that anything in the windowing functions section will
> disappear?
Who's to say?
I have no objection to looki
2008/9/2 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> 2008/9/1 Tom Lane <[EMAIL PROTECTED]>:
>>> However, since this is a behavioral change that could break code that
>>> works now, I think it should be a HEAD-only change; no backpatch.
>
>> I agree - it's could br
Trying to parse and bind the following:
COPY (SELECT $1::INT) TO STDOUT
gives a correct parsing-done, but then in the parameterdescription tells
me that there are no parameters.
Is this intended?
Is this a limitation of the COPY statement that will not change?
In that case, might I suggest th
Tom Lane wrote:
David Fetter <[EMAIL PROTECTED]> writes:
On Tue, Sep 02, 2008 at 02:42:25AM -0400, Tom Lane wrote:
It's not like we haven't seen a SQL draft go down in flames before.
Do you think that anything in the windowing functions section will
disappear?
Who's to say?
I have no obje
2008/9/2 Heikki Linnakangas <[EMAIL PROTECTED]>:
> Gregory Stark wrote:
>> What would the executor do for a query like
>>
>> SELECT lead(x,1),lead(y,2),lead(y,3)
>>
>> It would not only have to keep a tuplestore to buffer the output but it
>> would
>> have to deal with receiving data from different
On Sat, 2008-08-30 at 02:04 +0900, Hitoshi Harada wrote:
> Here's the latest window functions patch against HEAD. It seems to be
> ready for the September commit fest, as added documents, WINDOW clause
> feature and misc tests. I guess this would be the window functions
> feature freeze for 8.4.
On Fri, 2008-08-29 at 10:47 +0300, Heikki Linnakangas wrote:
> - Per comments and discussion with Simon, I've changed the "bubble up"
> behavior so that when a bottom-level page is updated, if the amount of
> free space was decreased, the change is not immediately bubbled up to
> upper page. I
On Fri, 2008-08-29 at 18:55 +0300, Heikki Linnakangas wrote:
> Tom Lane wrote:
> > Gregory Stark <[EMAIL PROTECTED]> writes:
> >> One idea, we could scan the rest of the current page and use the first
> >> match.
> >
> >> Another, given the way your tree structure works you can also descend the
On Thu, 2008-08-28 at 19:57 -0700, Ryan Bradetich wrote:
> I am not sure of the status of the patch, but I did read through the
> thread at:
>http://archives.postgresql.org/pgsql-hackers/2008-08/msg00054.php
>
>
> I just wanted to throw out another possible use for this GUC. There
> maybe
Hello all,
On Mon, Aug 11, 2008 at 2:24 AM, Gregory Stark <[EMAIL PROTECTED]> wrote:
>
> "Ryan Bradetich" <[EMAIL PROTECTED]> writes:
>
> > After a cursory glance at the HeapTupleHeaderData structure, it appears it
> > could be aligned with INTALIGN instead of MAXALIGN. The one structure I was
> >
Hello Simon,
On Mon, Sep 1, 2008 at 9:35 AM, Simon Riggs <[EMAIL PROTECTED]> wrote:
> On Thu, 2008-08-28 at 19:57 -0700, Ryan Bradetich wrote:
>> I just wanted to throw out another possible use for this GUC. There
>> maybe a better way to
>> solve this problem, but I believe this patch would be
Simon Riggs <[EMAIL PROTECTED]> wrote:
> > Why do we need to set rmgr_hook in _PG_init(), and add or mofify rmgrs
> > in our hook functions?
>
> If we modify RmgrTable in _PG_init() then we would have to have that
> structure available in all backends, which was a stated objective to
> avoid. We
2008/9/2 Ryan Bradetich <[EMAIL PROTECTED]>:
> Hello Simon,
>
> On Mon, Sep 1, 2008 at 9:35 AM, Simon Riggs <[EMAIL PROTECTED]> wrote:
>> On Thu, 2008-08-28 at 19:57 -0700, Ryan Bradetich wrote:
>>> I just wanted to throw out another possible use for this GUC. There
>>> maybe a better way to
>>>
On Mon, 2008-09-01 at 21:00 +0300, Heikki Linnakangas wrote:
> 1. It's important that what gets committed now can be extended to handle
> all of the window function stuff in SQL2003 in the future, as well as
> user-defined-window-functions in the spirit of PostgreSQL extensibility.
> Even if w
On Tue, 2008-09-02 at 18:30 +0900, ITAGAKI Takahiro wrote:
> Simon Riggs <[EMAIL PROTECTED]> wrote:
>
> > > Why do we need to set rmgr_hook in _PG_init(), and add or mofify rmgrs
> > > in our hook functions?
> >
> > If we modify RmgrTable in _PG_init() then we would have to have that
> > structu
On Tue, Sep 02, 2008 at 01:49:43AM -0700, Ryan Bradetich wrote:
> For fun, I looked around in heap_form_tuple() today to see how big of a job
> this
> change would be. It did not seem very hard to implement. I know there are
> probably several other places I missed with this patch, but this pat
On Tue, Sep 02, 2008 at 10:44:31AM +0100, Simon Riggs wrote:
> If we only have the combined (brain * time) to get a partial
> implementation in for this release then I would urge we go for that,
> rather than wait for perfection - as long as there are no other negative
> effects.
"premature optimi
On 9/1/08, Marko Kreen <[EMAIL PROTECTED]> wrote:
> First a correction, overriding malloc/free seems dangerous they
> seems to leak out, so correct would be to use YYMALLOC/YYFREE.
> This leaves 1.875 potentially leaking, but danger seems small.
Here is the safer patch. As the chance for the le
ITAGAKI Takahiro wrote:
I see that RmgrTable should be malloc'd when required,
but there is another issue; when to load rmgr libraries.
Rmgr objects are needed only in startup process during recovery.
If we want to reduce resource consumption by rmgrs, I think it is
better not to load rmgr libra
On 8/28/08, ITAGAKI Takahiro <[EMAIL PROTECTED]> wrote:
> Here is a contrib version of auto-explain.
> You can use shared_preload_libraries or local_preload_libraries to
> load the module automatically. If you do so, you also need to add
> "explain" in custom_variable_classes and define explain
"Marko Kreen" <[EMAIL PROTECTED]> wrote:
> On 8/28/08, ITAGAKI Takahiro <[EMAIL PROTECTED]> wrote:
> > You can use shared_preload_libraries or local_preload_libraries to
> > load the module automatically. If you do so, you also need to add
> > "explain" in custom_variable_classes and define ex
On 9/2/08, ITAGAKI Takahiro <[EMAIL PROTECTED]> wrote:
> "Marko Kreen" <[EMAIL PROTECTED]> wrote:
> > On 8/28/08, ITAGAKI Takahiro <[EMAIL PROTECTED]> wrote:
> > > You can use shared_preload_libraries or local_preload_libraries to
> > > load the module automatically. If you do so, you also nee
$ mkdir build
$ cd build
$ ../PostgreSQL.dev/configure
$ make
[...]
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing
-fwrapv -fpic -I/home/marko/src/build/../PostgreSQL.dev/src/pl/plpgsql/src
-I../../../../src/include
-I/home/marko
On Tue, 2008-09-02 at 13:38 +0300, Heikki Linnakangas wrote:
> There's one more reason to use shared_preload_libraries. It provides a
> sanity check that the library required for recovery is present and
> can
> be loaded, even when no recovery is required. If you have
> misconfigured
> your sys
Marko Kreen wrote:
$ mkdir build
$ cd build
$ ../PostgreSQL.dev/configure
$ make
[...]
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing
-fwrapv -fpic -I/home/marko/src/build/../PostgreSQL.dev/src/pl/plpgsql/src
-I../../../../src/
On Tue, 2008-09-02 at 03:14 -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Tue, Sep 02, 2008 at 02:42:25AM -0400, Tom Lane wrote:
> >> It's not like we haven't seen a SQL draft go down in flames before.
>
> > Do you think that anything in the windowing functions section
Radek Strnad wrote:
- new collations can be defined with command CREATE COLLATION name> FOR FROM
[STRCOLFN ]
[ ] [ ] [ LCCOLLATE ]
[ LCCTYPE ]
How do you plan to make a collation case sensitive or accent sensitive?
I have previously commented that this is not a realistic view on how
David Rowley wrote:
Reference: Bruce Momjian writes: ->
http://archives.postgresql.org/pgsql-committers/2007-09/msg00402.php
Other references: Boyer Moore?? ->
http://www.cs.utexas.edu/users/moore/best-ideas/string-searching/fstrpos-example.html
I look forward to receiving feedback on this.
On Tue, Sep 02, 2008 at 02:50:47PM +0300, Peter Eisentraut wrote:
> Radek Strnad wrote:
> >- new collations can be defined with command CREATE COLLATION >name> FOR FROM
> >[STRCOLFN ]
> >[ ] [ ] [ LCCOLLATE ]
> >[ LCCTYPE ]
>
> How do you plan to make a collation case sensitive or accent
Marko Kreen wrote:
In the meantime, here is simple patch for case-insensivity.
You might be able to talk me into accepting various unambiguous, common
alternative spellings of various units. But for instance allowing MB
and Mb to mean the same thing is insane.
--
Sent via pgsql-hackers mai
I think at least case sensitivity can be done by comparing two strings
converted to upper case with toupper() function.
Regards
Radek Strnad
>
> On Tue, Sep 2, 2008 at 2:00 PM, Martijn van Oosterhout <[EMAIL
> PROTECTED]>wrote:
>
>> On Tue, Sep 02, 2008 at 02:50:47PM +0300, Peter Eisentraut wro
2008/9/2 Simon Riggs <[EMAIL PROTECTED]>:
> If you've done all of that, then I'm impressed. Well done.
>
> Few general comments
>
> * The docs talk about "windowing functions", yet you talk about "window
> functions" here. I think the latter is correct, but whichever we choose
> we should be consis
$ grep -i D2MDIR * -R
doc/src/sgml/Makefile:D2MSCRIPT= $(D2MDIR)/docbook2man-spec.pl
I could not find anything in the code related to this. I am trying to
create man pages in -HEAD, and getting an error:
[EMAIL PROTECTED] sgml]$ make man
onsgmls -D . postgres.sgml | sgmlspl /docbook2man-spec.pl
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Marko Kreen wrote:
>> In the meantime, here is simple patch for case-insensivity.
>
> You might be able to talk me into accepting various unambiguous, common
> alternative spellings of various units. But for instance allowing MB and Mb
> to
> mean t
On Sun, 31 Aug 2008, Alvaro Herrera wrote:
Greg Smith wrote:
This patch does need a bit of general care in a couple of areas. The
reviewing game plan I'm working through goes like this:
Did this review effort go anywhere?
Haven't made much progress--all my spare time for work like this la
Hi Heikki,
I'm sorry for lack of explanation. It is my fault.
Heikki says (on commit fest wiki):
I believe I debunked this patch enough already. Apparently there's some
compatibility issue between 32-bit and 64-bit Sparcs, but this patch
didn't catch that. It doesn't seem like thi
Hitoshi Harada wrote:
2008/9/2 Heikki Linnakangas <[EMAIL PROTECTED]>:
In my understanding, the "Window Frame" is defined
by clauses such like "ROWS BETWEEN ... ", "RANGE BETWEEN ... " or so,
contrast to "Window Partition" defined by "PARTITION BY" clause. A
frame slides within a partition or the
Martijn van Oosterhout wrote:
On Tue, Sep 02, 2008 at 10:44:31AM +0100, Simon Riggs wrote:
If we only have the combined (brain * time) to get a partial
implementation in for this release then I would urge we go for that,
rather than wait for perfection - as long as there are no other negative
ef
Zdenek Kotala wrote:
Hi Heikki,
I'm sorry for lack of explanation. It is my fault.
Heikki says (on commit fest wiki):
I believe I debunked this patch enough already. Apparently there's some
compatibility issue between 32-bit and 64-bit Sparcs, but this patch
didn't catch that. It
Martijn van Oosterhout wrote:
On Tue, Sep 02, 2008 at 02:50:47PM +0300, Peter Eisentraut wrote:
Radek Strnad wrote:
- new collations can be defined with command CREATE COLLATION name> FOR FROM
[STRCOLFN ]
[ ] [ ] [ LCCOLLATE ]
[ LCCTYPE ]
How do you plan to make a collation case sensiti
Gregory Stark wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
Marko Kreen wrote:
In the meantime, here is simple patch for case-insensivity.
You might be able to talk me into accepting various unambiguous, common
alternative spellings of various units. But for instance allowing MB and Mb
On 9/2/08, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Marko Kreen wrote:
> > In the meantime, here is simple patch for case-insensivity.
>
> You might be able to talk me into accepting various unambiguous, common
> alternative spellings of various units. But for instance allowing MB and Mb
> t
On 9/2/08, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Gregory Stark wrote:
> > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > > Marko Kreen wrote:
> > > > In the meantime, here is simple patch for case-insensivity.
> > > >
> > > You might be able to talk me into accepting various unambiguous,
Marko Kreen escribió:
> $ mkdir build
> $ cd build
> $ ../PostgreSQL.dev/configure
> $ make
> [...]
> gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith
> -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing
> -fwrapv -fpic -I/home/marko/src/build/../PostgreSQL.dev/src/pl/plpgsql/src
>
On 9/2/08, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Marko Kreen escribió:
> > $ mkdir build
> > $ cd build
> > $ ../PostgreSQL.dev/configure
> > $ make
> > [...]
> > gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith
> > -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing
>
Marko Kreen escribió:
> On 9/2/08, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> > Marko Kreen escribió:
> > > error: pl_gram.h: No such file or directory
> >
> > Try running "make maintainer-clean" -- see
> >
> >
> > http://archives.postgresql.org/message-id/20080829162252.GG3983%40alvh.no-ip.or
At 2008-09-02 15:10:23 +0300, [EMAIL PROTECTED] wrote:
>
> [EMAIL PROTECTED] sgml]$ make man
As Alvaro noted recently, you need to use "make man D2MDIR=/some/path".
-- ams
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.post
On Tue, 2008-09-02 at 19:47 +0530, Abhijit Menon-Sen wrote:
> > [EMAIL PROTECTED] sgml]$ make man
>
> As Alvaro noted recently,
I probably missed that.
> you need to use "make man D2MDIR=/some/path".
Thanks :)
Cheers.
--
Devrim GÜNDÜZ, RHCE
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gu
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Marko Kreen escribió:
>> I'll try with new cvs checkout.
> That'll have the same effect as make maintainer-clean, and should work
> equally well.
No, it'll work better. The real problem here is that in the CVS-HEAD
makefiles, "make maintainer-clean" f
Abhijit Menon-Sen <[EMAIL PROTECTED]> writes:
> At 2008-09-02 15:10:23 +0300, [EMAIL PROTECTED] wrote:
>>
>> [EMAIL PROTECTED] sgml]$ make man
> As Alvaro noted recently, you need to use "make man D2MDIR=/some/path".
I see it's been like that for quite some time, but still it seems pretty
bogus.
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> 2008/9/2 Tom Lane <[EMAIL PROTECTED]>:
>> BTW, there are actually two separate issues here: input parameters and
>> output parameters. After brief thought it seems like we should enforce
>> uniqueness of non-omitted parameter names for IN parameters (i
2008/9/2 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> 2008/9/2 Tom Lane <[EMAIL PROTECTED]>:
>>> BTW, there are actually two separate issues here: input parameters and
>>> output parameters. After brief thought it seems like we should enforce
>>> uniqueness of non
"Ryan Bradetich" <[EMAIL PROTECTED]> writes:
> The patch concept is fairly simple.
>1. Add a new boolean local variable: require_max_align
> (initialized to false).
This really can't possibly work, because you'd need to propagate
knowledge of the tuple's alignment requirement all over the pl
"Marko Kreen" <[EMAIL PROTECTED]> writes:
> Uh. So you want force "proper" units in presentations at the price
> of everyday admin operations? Does not seem like a sensible tradeoff.
It didn't to anyone else when Peter wrote the current version either, but as
the person willing to actually do t
"Ryan Bradetich" <[EMAIL PROTECTED]> writes:
>4. If require_max_align = true, use the MAXALIGN macro; otherwise
> use the INTALIGN macro.
Huh, I didn't think of doing it like that.
But I'm confused. You seem to be tweaking the alignment of the data inside the
tuple? After the tuple header? I
Tom Lane <[EMAIL PROTECTED]> writes:
> "Ryan Bradetich" <[EMAIL PROTECTED]> writes:
>> The patch concept is fairly simple.
>
>>1. Add a new boolean local variable: require_max_align
>> (initialized to false).
>
> This really can't possibly work, because you'd need to propagate
> knowledge of
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Tue, 2008-09-02 at 18:30 +0900, ITAGAKI Takahiro wrote:
>> How about adding a new variable "recovery_preload_libaries" like as
>> shared_preload_libraries? Rmgr libs in it are loaded only in startup
>> process and only if recovery is needed.
> Good poin
Tom Lane wrote:
Abhijit Menon-Sen <[EMAIL PROTECTED]> writes:
At 2008-09-02 15:10:23 +0300, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] sgml]$ make man
As Alvaro noted recently, you need to use "make man D2MDIR=/some/path".
I see it's been like that for quite some time, but still it seems p
On Tue, Sep 02, 2008 at 04:46:16PM +0300, Peter Eisentraut wrote:
> >While it's true POSIX locales don't handle this, other collation
> >libraries do and we should support them if the user wants.
>
> Do they handle exactly those two attributes specifically? Can you point
> out references? Or do
On Sep 1, 2008, at 22:31, Brendan Jurd wrote:
Oh, another thing: it shouldn't be STRICT. Nulls have perfectly good
types.
Agreed.
Barring any further comments/objections, I'll go ahead and prepare a
patch to add this to core.
So it will return a text representation or an Oid?
Best,
David
Hello Martijn,
> You need to arrange testing on an architechture that has strict
> alignment reuiqrements. For example i386 doesn't care about alignment
> at all and will anything from anywhere, with performance degradation.
>
> Other architechtures will simply throw exceptions, that's the smoke
>
On Tue, 2008-09-02 at 18:40 +0300, Peter Eisentraut wrote:
> The documentation says that
Even though I could not find it, here is an error:
$ make man.tar.gz D2MDIR=/usr/share/sgml/docbook/utils-0.6.14/helpers/
make -C sgml man
make[1]: Entering directory `/home/devrim/PostgreSQL/pgsql/doc/src/sg
Hi,
I'm having a hard time using an index scan. So far, I've done quite well
with ScanKeyInit for equality searches. But now I need to scan an index
from a given starting point. Something like:
(x, y, z,...) > (const, const, const,...)
For the equality operatior, I've used get_sort_group_
On Tue, 2008-09-02 at 19:07 +0300, Devrim GÜNDÜZ wrote:
>
> On Tue, 2008-09-02 at 18:40 +0300, Peter Eisentraut wrote:
> > The documentation says that
Oh, sorry -- I had missed the remaining part of your e-mail.
--
Devrim GÜNDÜZ, RHCE
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux
On Tue, 2008-09-02 at 11:39 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Tue, 2008-09-02 at 18:30 +0900, ITAGAKI Takahiro wrote:
> >> How about adding a new variable "recovery_preload_libaries" like as
> >> shared_preload_libraries? Rmgr libs in it are loaded only in sta
Hello Tom,
On Tue, Sep 2, 2008 at 8:07 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Ryan Bradetich" <[EMAIL PROTECTED]> writes:
>> The patch concept is fairly simple.
>
>>1. Add a new boolean local variable: require_max_align
>> (initialized to false).
>
> This really can't possibly work, becau
Hello Greg,
On Tue, Sep 2, 2008 at 8:30 AM, Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Ryan Bradetich" <[EMAIL PROTECTED]> writes:
>
>>4. If require_max_align = true, use the MAXALIGN macro; otherwise
>> use the INTALIGN macro.
>
> Huh, I didn't think of doing it like that.
>
> But I'm confus
On Tue, Sep 02, 2008 at 12:42:45PM +0100, Simon Riggs wrote:
>
> On Tue, 2008-09-02 at 03:14 -0400, Tom Lane wrote:
> > David Fetter <[EMAIL PROTECTED]> writes:
> > > On Tue, Sep 02, 2008 at 02:42:25AM -0400, Tom Lane wrote:
> > >> It's not like we haven't seen a SQL draft go down in flames
> > >>
Gregory Stark <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> In particular, how would code *reading* the tuple know where the
>> data starts?
> Uh, at t_hoff, no?
Doh, right. Obviously need more caffeine.
regards, tom lane
--
Sent via pgsql-hac
Devrim GÜNDÜZ wrote:
> $ make man.tar.gz D2MDIR=/usr/share/sgml/docbook/utils-0.6.14/helpers/
> make -C sgml man
> make[1]: Entering directory `/home/devrim/PostgreSQL/pgsql/doc/src/sgml'
> onsgmls -D . postgres.sgml | sgmlspl
> /usr/share/sgml/docbook/utils-0.6.14/helpers//docbook2man-spec.pl -
Martijn van Oosterhout <[EMAIL PROTECTED]> writes:
> On Tue, Sep 02, 2008 at 04:46:16PM +0300, Peter Eisentraut wrote:
>> >While it's true POSIX locales don't handle this, other collation
>> >libraries do and we should support them if the user wants.
I think that's backwards. We have to go with
"Ryan Bradetich" <[EMAIL PROTECTED]> writes:
> Hello Greg,
>
> On Tue, Sep 2, 2008 at 8:30 AM, Gregory Stark <[EMAIL PROTECTED]> wrote:
>>
>> But I'm confused. You seem to be tweaking the alignment of the data inside
>> the
>> tuple? After the tuple header? I thought we had only one byte of waste
"Ryan Bradetich" <[EMAIL PROTECTED]> writes:
> On Tue, Sep 2, 2008 at 8:07 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> It's conceivable that we could make this work if we wanted to dedicate
>> an infomask bit to showing whether the tuple needs int or double
>> alignment. I don't really think it's w
On Tue, 2008-09-02 at 09:35 -0700, David Fetter wrote:
> On Tue, Sep 02, 2008 at 12:42:45PM +0100, Simon Riggs wrote:
> >
> > On Tue, 2008-09-02 at 03:14 -0400, Tom Lane wrote:
> > > David Fetter <[EMAIL PROTECTED]> writes:
> > > > On Tue, Sep 02, 2008 at 02:42:25AM -0400, Tom Lane wrote:
> > > >
On Tue, 2008-09-02 at 12:47 -0400, Alvaro Herrera wrote:
> > Unknown SDATA: [mdash ]
> at /usr/share/sgml/docbook/utils-0.6.14/helpers//docbook2man-spec.pl
> line 1241, line 11975.
>
> Please see here:
>
> http://archives.postgresql.org/message-id/20080821130203.GN4169%
> 40alvh.no-ip.org
Thank
Markus Wanner <[EMAIL PROTECTED]> writes:
> Hi,
>
> I'm having a hard time using an index scan. So far, I've done quite well with
> ScanKeyInit for equality searches. But now I need to scan an index from a
> given
> starting point. Something like:
>
>(x, y, z,...) > (const, const, const,...)
On Tue, Sep 02, 2008 at 05:42:13PM +0100, Gregory Stark wrote:
> Martijn van Oosterhout <[EMAIL PROTECTED]> writes:
> > On Tue, Sep 02, 2008 at 04:46:16PM +0300, Peter Eisentraut wrote:
> >> >While it's true POSIX locales don't handle this, other collation
> >> >libraries do and we should support t
The description of the CommitFestBlank template suggests that it sets up
an editable page for you, but AFAICT it does no such thing. I had to
manually create all the right sections:
http://wiki.postgresql.org/index.php?title=CommitFest:2008-11&diff=2260&oldid=2258
in order to have a page that peop
On Tue, Sep 02, 2008 at 08:58:04AM -0700, David E. Wheeler wrote:
> >Barring any further comments/objections, I'll go ahead and prepare a
> >patch to add this to core.
>
> So it will return a text representation or an Oid?
Hopefully regtype. The function doesn't need changing, but then users
can
On Sep 2, 2008, at 08:58, David E. Wheeler wrote:
On Sep 1, 2008, at 22:31, Brendan Jurd wrote:
Oh, another thing: it shouldn't be STRICT. Nulls have perfectly
good
types.
Agreed.
Barring any further comments/objections, I'll go ahead and prepare a
patch to add this to core.
So it will
On Sep 2, 2008, at 10:43, David E. Wheeler wrote:
Looks like regtype displays as an integer. So how about
pg_regtypeof() and pg_typeof()?
Sorry, make that:
PG_FUNCTION_INFO_V1(pg_regtypeof);
Datum
pg_regtypeof(PG_FUNCTION_ARGS)
{
PG_RETURN_OID(get_fn_expr_argtype(fcinfo->flinfo, 0));
}
Markus Wanner <[EMAIL PROTECTED]> writes:
> I'm having a hard time using an index scan. So far, I've done quite well
> with ScanKeyInit for equality searches. But now I need to scan an index
> from a given starting point. Something like:
> (x, y, z,...) > (const, const, const,...)
> For the
"David E. Wheeler" <[EMAIL PROTECTED]> writes:
> Looks like regtype displays as an integer.
Better try that again.
regression=# select 1043::regtype;
regtype
---
character varying
(1 row)
regression=#
I see no need for two functions here.
r
Gregory Stark <[EMAIL PROTECTED]> writes:
> The other 4 bytes you could save is by packing the whole tuples themselves
> more closely on the page. That happens when the item pointer is added and
> pointed to the tuple. To do that heap_form_tuple would have to return data
> back to the caller about
On Sep 2, 2008, at 11:06, Tom Lane wrote:
Better try that again.
regression=# select 1043::regtype;
regtype
---
character varying
(1 row)
regression=#
I see no need for two functions here.
Oh. I tried:
try=# select 1::regtype;
regtype
-
1
I had assumed that
Radek Strnad escribió:
> Ok, so do you suggest to leave it with a notice "reindex database" or start
> to solve it somehow?
I don't know. If there are two tasks that need the same treatment, it
seems a safe conclusion that they need a common solution.
--
Alvaro Herrera
Hi,
Gregory Stark wrote:
It's right for your equality case which is effectively x=const, y=const,
z=const. It's not for row comparisons case for which you need a funny "header"
ScanKey. See the comments in access/skey.h, search for "row comparisons". I'm
not sure if there's a function to create
Martijn van Oosterhout <[EMAIL PROTECTED]> writes:
> And I think that's backwards. Why can we only use a feature once every
> OS out there implements it? We still run on systems that don't have SSL
> support. LC_TYPE settings are not portable between systems, yet that
> doesn't bother anyone. Why s
Zdenek Kotala napsal(a):
32/64 bit issue is little bit different story and it is general (not
only SPARC but on SPARC has bigger impact). Problem is that CRC32 gives
probably different result when it is compiled 32bit or 64bit. I'm going
to examine it more.
I'm sorry about noise. Everythin
Hi,
Devrim has been trying to set up RPM files for 8.4devel. However, the
tarballs he is generating are not alike those found in our FTP site;
official ones include manpages and HTML docs as man.tar.gz and
postgres.tar.gz, but a simple "make dist" does not seem to include them.
I'm wondering how
"Marko Kreen" <[EMAIL PROTECTED]> writes:
> On 9/1/08, Marko Kreen <[EMAIL PROTECTED]> wrote:
>> First a correction, overriding malloc/free seems dangerous they
>> seems to leak out, so correct would be to use YYMALLOC/YYFREE.
>> This leaves 1.875 potentially leaking, but danger seems small.
> Her
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I'm wondering how are these things supposed to be generated. Does Marc
> create the regular tarballs using "make dist", and then unpack them and
> include the other tarballs inside? Does he use a different make target?
I think you need "make distprep"
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Marko Kreen" <[EMAIL PROTECTED]> writes:
>> Uh. So you want force "proper" units in presentations at the price
>> of everyday admin operations? Does not seem like a sensible tradeoff.
> It didn't to anyone else when Peter wrote the current version eit
Anything that will reduce potential downtime should be way to go.
To me it seems that Peter uses the loudest voice and others just don't care
enough.
Using kB for kilobyte seems quite alien and confusing. I have not noticed
that to be used in software i use in my everyday work and could not find a
Hello Greg,
On Tue, Sep 2, 2008 at 9:54 AM, Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Ryan Bradetich" <[EMAIL PROTECTED]> writes:
> The structure on the page is to have a bunch of tuples stored one after the
> other. Each tuple is maxaligned after the previous (actually before the
> previous sin
Hello Tom,
> Well, as Greg pointed out, setting t_hoff correctly should be sufficient
> for squeezing out useless padding between the tuple header and the tuple
> data. The real objection here is that that's leaving most of the
> possible gain still on the table. The tuple *as a whole* (header a
On Tue, Sep 2, 2008 at 9:35 AM, David Fetter <[EMAIL PROTECTED]> wrote:
> Any chance we can buy a few copies of the official one for use on the
> project?
AFAIK there is no significant difference between the "official"
standard and the draft version available online, so I don't see the
point.
Nei
Brian Hurt wrote:
> So I thought upping the debug level of postgres would help, by adding
> a -o '-d 5' to the pg_ctl command line. The log file that gets spit
> out in this case is attached. What is noticeable is how unhelpfull
> it is.
I think this is just the stderr. The rest of the err
=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <[EMAIL PROTECTED]> writes:
> Pre-sorting introduced one problem (see XXX in code): it's not easy
> anymore to get the minimal frequency of MCELEM values. I was using it to
> assert that the selectivity of a tsquery node containing a lexeme not in
> MCELEM is no
1 - 100 of 127 matches
Mail list logo
