On Sat, Jun 23, 2007 at 12:02:43PM -0400, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> >> One thing I've thought about doing is to remove the default in initdb
> >> completely and *force* the user to choose auth type. Packagers can
> >> then just use that to set ident or whatever
On Fri, 22 Jun 2007, Tom Lane wrote:
What's wrong with synchronous_commit? It's accurate and simple.
It's kind of a big word that not a lot of people understand the subtleties
of, and I'd be concerned it will sow confusion with the terminology used
for WAL synchronous writes.
When I expla
On Fri, 2007-06-22 at 16:25 -0500, Kevin Grittner wrote:
> I apologize for not grabbing more information before the evidence was gone,
> but I think there may be a vulnerability to database corruption on PITR
> recovery if a stop is done with the "fast" option right after a database logs
> "archive
On Sat, 23 Jun 2007, Euler Taveira de Oliveira wrote:
Will it be possible to disable stemming or stopwords removal? I'm asking
this 'cause sometimes stemming doesn't lead to good results and/or
stopwords are relevant. Maybe it could be an GUC variables
('enable_stemming' and 'enable_stopwords').
Tatsuo Ishii wrote:
> japanese '{ja_JP, C}'
>
> How would we know C -> japanese?
>
You can't do that. You can't have different languages (not locales)
mapping to the same 'tsearch language' because the stemmer doesn't know
that a specific word is in english or japanese. So you have two options:
On Jun 23, 2007, at 11:03 AM, Magnus Hagander wrote:
I would also argue that trust auth is not such an evil option that we
mustn't allow it to be the default. On a single-user machine it's
actually perfectly sane, seeing that we don't allow TCP connections
by default.
Is there really such
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Magnus Hagander <[EMAIL PROTECTED]> writes:
One thing I've thought about doing is to remove the default in initdb
completely and *force* the user to choose auth type.
>
>>> I'll object if no one else doe
Alvaro Herrera wrote:
> What I was really suggesting was having a table mapping locale names
> into "tsearch languages". Then the configuration could be made based on
> the language, not on the locale name. So the stopword list is for
> "russian", regardless of whether the locale is Russian_Russ
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Magnus Hagander <[EMAIL PROTECTED]> writes:
>>> One thing I've thought about doing is to remove the default in initdb
>>> completely and *force* the user to choose auth type.
>> I'll object if no one else does: this will break existi
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>>> One thing I've thought about doing is to remove the default in initdb
>>> completely and *force* the user to choose auth type. Packagers can
>>> then just use that to set ident or whatever. and interactive users
>>> can pick trust if
Magnus Hagander <[EMAIL PROTECTED]> writes:
>> One thing I've thought about doing is to remove the default in initdb
>> completely and *force* the user to choose auth type. Packagers can
>> then just use that to set ident or whatever. and interactive users
>> can pick trust if they really need it,
Andrew Dunstan wrote:
>
>
> Magnus Hagander wrote:
>> Magnus Hagander 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 wh
Magnus Hagander wrote:
Magnus Hagander 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 would
prompt for the
Magnus Hagander 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 would
>>> prompt for the postgres user passwo
Magnus Hagander wrote:
> On Thu, Jun 07, 2007 at 01:12:06PM +0200, Peter Eisentraut wrote:
>> Magnus Hagander wrote:
>>> Is this script in CVS somewhere? I know it's not in the main backend
>>> repo.
>> Most of what these scripts have done in the past has been systematized
>> and folded into the "
15 matches
Mail list logo
