Dennis Bjorklund said:
> On Sun, 25 Apr 2004, Andrew Dunstan wrote:
>
>> >> Why do you want two names? Just keep the original casing, and a
>> >> boolean saying if it's quoted or not.
>>
>> Sorry - brain malfunction - yes, original casing plus boolean would
>> work. In effect you could derive the
On Sun, 25 Apr 2004, Andrew Dunstan wrote:
> >> Why do you want two names? Just keep the original casing, and a boolean
> >> saying if it's quoted or not.
>
> Sorry - brain malfunction - yes, original casing plus boolean would
> work. In effect you could derive the canonical form from those tw
(To resurrect an old thread, I've finally got some time to devote to
this; I'll post a patch once I've got something ready for public
consumption.)
On 23-Mar-04, at 4:59 PM, Tom Lane wrote:
Let's see ... fleshing out this idea a bit, here's a rundown of all the
symbols in pg_list.h and suggested
FreeBSD 4.X will not support --enable-thread-safety in 7.5. Let me
explain why.
In 7.4, if we didn't have a *_r function, and the non-*_r function was
not thread-safe, we called the non-*_r function with thread locks and
copied the value into the passed storage pointer. I thought that was
OK, bu
On -performance we have been discussing a configuration where a bulk
delete run takes almost a day (and this is not due to crappy hardware or
apparent misconfiguration). Unless I misinterpreted the numbers,
btbulkdelete() processes 85 index pages per second, while lazy vacuum is
able to clean up 6
A sort of debate started by Bruce about what MySQL does better vs what
PostgreSQL could do, then there was a thread about removing "/contrib"
from the main download, and a few other posts.
I don't think these are unrelated. They all fall under the umbarella of
"How does a new user come to use Post
Peter Eisentraut wrote:
> Rob wrote:
> > But I think there is room to go further, I don't see any reason why
> > that default install can't include example DBs,
>
> One reason is that a useful example database would likely have a
> download footprint of 10 MB or more. Having this in the default
On Mon, 19 Apr 2004 12:00:10 -0400, Tom Lane <[EMAIL PROTECTED]> wrote:
>A possible compromise is to limit the number of pages sampled to
>something a bit larger than n, perhaps 2n or 3n. I don't have a feeling
>for the shape of the different-pages probability function; would this
>make a signific
I wrote:
Alvaro Herrera wrote:
On Sun, Apr 25, 2004 at 12:23:55PM -0400, Andrew Dunstan wrote:
I don't think we should rush at this. All of these solutions are
based on the existing structures. I have started thinking about a
solution that would involve keeping two versions of catalog n
Alvaro Herrera wrote:
On Sun, Apr 25, 2004 at 12:23:55PM -0400, Andrew Dunstan wrote:
I don't think we should rush at this. All of these solutions are based
on the existing structures. I have started thinking about a solution
that would involve keeping two versions of catalog names: a cano
On Sun, Apr 25, 2004 at 12:23:55PM -0400, Andrew Dunstan wrote:
> I don't think we should rush at this. All of these solutions are based
> on the existing structures. I have started thinking about a solution
> that would involve keeping two versions of catalog names: a canonical
> name and a "n
Shachar Shemesh wrote:
I'm opening a new thread, as the previous one was too nested, and
contained too much emotions.
I'll start by my understanding of a summary of the thread so far. The
solution we are seeking would have to satisfy the following conditions:
1. Setting should be on a per-dat
Rod Taylor wrote:
5. If the identifier is lowercase only, convert it to uppercase only. I
am assuming here that the authors of the client code chose an
uppercase-folding database, so they should know what they are doing when
accessing stuff from the standard offering.
You've just broken on
> I'm not sure you understood me.
Perhaps not, here is what we have:
\c template_db
CREATE TABLE "example" ( "col" integer);
CREATE DATABASE newdb WITH TEMPLATE template_db UPPERCASE IDENTIFIERS;
\c newdb
SELECT "col" FROM "example";
> In short, I don't think this suggestion broke your databa
> 5. If the identifier is lowercase only, convert it to uppercase only. I
> am assuming here that the authors of the client code chose an
> uppercase-folding database, so they should know what they are doing when
> accessing stuff from the standard offering.
You've just broken one of my databas
I'm opening a new thread, as the previous one was too nested, and
contained too much emotions.
I'll start by my understanding of a summary of the thread so far. The
solution we are seeking would have to satisfy the following conditions:
1. Setting should be on a per-database level. A per-server
Rob wrote:
> But I think there is room to go further, I don't see any reason why
> that default install can't include example DBs,
One reason is that a useful example database would likely have a
download footprint of 10 MB or more. Having this in the default
download would not be appreciated b
17 matches
Mail list logo
