On Wed, 2005-12-10 at 18:02 -0400, Bill Bartlett wrote:
> [snipped]
>
> > May not be the best choice on Windows for production use, though for
> > development, it should be adequate.
>
> Are there known issues with the Windows version for production use, or
> is this simply because of the rela
Here's one (of many) solutions:
CREATE OR REPLACE FUNCTION range( ANYELEMENT, ANYARRAY ) RETURNS INTEGER
LANGUAGE SQL AS
'SELECT CASE array_upper( $2, 1 ) WHEN 1 THEN 0 ELSE range( $1, $2[
1:(array_upper( $2, 1 ) - 1) ] ) END
+ CASE WHEN $1 > $2[ array_upper( $2, 1 ) ] THEN 1 ELSE 0 END;
I have to admit, my thoughts on it were to build a query with case
statements in it and execute it. That sounds about like you're
proposing, right?
On Thu, 2005-10-13 at 11:30, Dean Gibson (DB Administrator) wrote:
> What's the point of a binary search if the list is small enough to fit
> on a l
Scott Marlowe <[EMAIL PROTECTED]> writes:
> I could see how it might be possible to make a two argument user defined
> function that took an argument like:
> select intvl(10,'20 30 40 50 60');
> so that the multiple arguments are really just a space or comma
> separated list fed to the function.
What's the point of a binary search if the list is small enough to fit
on a line or two? And if a query can be substituted for N1-NN, you have
to read all the values anyway, and then the function is trivially
expressed as a normal query with no decrease in speed.
-- Dean
On Wed, 2005-10-12 a
On Thu, Oct 13, 2005 at 10:46:29AM -0500, Scott Marlowe wrote:
> choice in another. So, multi-master replication isn't likely to become
> a plug in module for postgresql any time soon.
It's not even a thing, so it can't become a plug-in.
Consider just two kinds of multi-master:
1. Oracle's
On Wed, 2005-10-12 at 20:08, Michael Fuhr wrote:
> On Wed, Oct 12, 2005 at 04:49:59PM -0500, Scott Marlowe wrote:
> > On Wed, 2005-10-12 at 16:16, Chris Travers wrote:
> > > Compared to MySQL, I can't think of any downsides. All relevant
> > > usability issues have been solved, though there are s
On Wed, 2005-10-12 at 23:11, Chris Travers wrote:
> Scott Marlowe wrote:
> >Thought I'd comment on this.
> >
> >According to the author of the innodb engine, innodb uses MVCC.
> >OTOH, I consider innodb to be broken in production, due to issues with
> >constant growth and no way to reclaim the los
> > [snipped]
> >
> >> May not be the best choice on Windows for production use,
> though for
> >> development, it should be adequate.
> >
> > Are there known issues with the Windows version for
> production use, or
> > is this simply because of the relative newness of the
> Windows-native
I would like to believe that its the latter, it should improve with time.
On Wed, 12 Oct 2005, Bill Bartlett wrote:
>
>[snipped]
>
>> May not be the best choice on Windows for production use, though for
>> development, it should be adequate.
>
>Are there known issues with the Windows version for
Bill Bartlett wrote:
[snipped]
May not be the best choice on Windows for production use, though for
development, it should be adequate.
Are there known issues with the Windows version for production use, or
is this simply because of the relative newness of the Windows-native
version?
Perfor
[snipped]
> May not be the best choice on Windows for production use, though for
> development, it should be adequate.
Are there known issues with the Windows version for production use, or
is this simply because of the relative newness of the Windows-native
version?
- Bill
-
On Wed, 2005-10-12 at 16:49 -0500, Scott Marlowe wrote:
> On Wed, 2005-10-12 at 16:16, Chris Travers wrote:
> > Denis G Dudhia wrote:
> >
> > > Hello There...
> > >
> > > I am new to PostgreSQL.
> > >
> > > I usually check out negative sides of any software or system, before
> > > implementing it
Scott Marlowe wrote:
On Wed, 2005-10-12 at 16:16, Chris Travers wrote:
Denis G Dudhia wrote:
Hello There...
I am new to PostgreSQL.
I usually check out negative sides of any software or system, before
implementing it or using it.
Compared to MySQL, I can't think of any dow
Wow, I must be missing something, because I cannot even dream up a case
where I think I might find a use for the mysql INTERVAL() function, far
less actually NEED it :)
Terry
Michael Fuhr wrote:
On Wed, Oct 12, 2005 at 04:49:59PM -0500, Scott Marlowe wrote:
On Wed, 2005-10-12 at 16:16, Chr
On Wed, Oct 12, 2005 at 04:49:59PM -0500, Scott Marlowe wrote:
> On Wed, 2005-10-12 at 16:16, Chris Travers wrote:
> > Compared to MySQL, I can't think of any downsides. All relevant
> > usability issues have been solved, though there are some functions like
> > INTERVAL that are not supported (
On Wed, 2005-10-12 at 16:16, Chris Travers wrote:
> Denis G Dudhia wrote:
>
> > Hello There...
> >
> > I am new to PostgreSQL.
> >
> > I usually check out negative sides of any software or system, before
> > implementing it or using it.
> >
> Compared to MySQL, I can't think of any downsides. Al
Denis G Dudhia wrote:
Hello There...
I am new to PostgreSQL.
I usually check out negative sides of any software or system, before
implementing it or using it.
Compared to MySQL, I can't think of any downsides. All relevant
usability issues have been solved, though there are some functions
On Mon, Oct 03, 2005 at 12:01:02PM -, Denis G Dudhia wrote:
> I would like to know the limitations of PostgreSQL.
>
> Also, I would like to know, whether there is any limitations for the
> number of records or the size of the tables or database in
> PostgreSQL?
See PostgreSQL FAQ.
Section 4.
Hello There...
I am new to PostgreSQL.
I usually check out negative sides of any software or system, before implementing it or using it.
I would like to know the limitations of PostgreSQL.
Also, I would like to know, whether there is any limitations for the number of records or the size of the
20 matches
Mail list logo