Possibly create a timeout for psql. pg_dump, pg_restore and other clients.
If they can not connect to a certain host within a certain period it will
quit with an error. I have psql's still running for 6 days from crontab
that could not connect to a bogus IP address.
I checked the idocs and search
> It occurred to me that a server with locale features that is started in
> the C locale is going to behave the same as a server without locale
> features. The exception are a few extra memory moving operations. (I
> sincerely hope that all systems' libcs have optimized paths for the C
> locale.
> Hi all. I'm not a good DB admin , thats why I'm posting to this list !
> How can I figure out the size of a database or table ???
It was easier in older versions of postgresql to perform a `du -h` on
the directory that corresponded to the database name. However now they
are named by some type o
Peter Eisentraut wrote:
>
> Hiroshi Inoue writes:
>
> > Hmm * string1 = string2 * doesn't imply * string1 LIKE string2 * ?
>
> In the current implementation of LIKE, you're right. The SQL standard
> allows for the possibility that "[d]epending on the collating sequence,
> two strings may compa
We're about to start up Postgresql in production, and I am looking for a
few tools, so I do not have to reinvent the wheel.
I'm looking for tools that:
1) Grep through log files, looking for particulary nasty items, that
should get sent to me in email or to a cell phone. I noticed you can u
Well, ability to lock only unlocked rows in select for update is useful,
of course. But uniq features of user'locks are:
1. They don't interfere with normal locks hold by session/transaction.
2. Share lock is available.
3. User can lock *and unlock objects* inside transaction, which is not
(a
If it's of any assistance, I'm working with the Open Source Database
Benchmark guys (osdb.sourceforge.net) to get an AS3AP-based benchmark
for PostgreSQL 7.1.x+ up-and-running reliably.
It's working on my Mandrake Linux 8.0 system here, but I need the main
OSDB guy to get back from holidays to re
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> (I sincerely hope that all systems' libcs have optimized paths for the C
> locale.) So we could get rid of this --enable-locale switch
> altogether.
Some experimental evidence to support the claim that --enable-locale has
zero cost would be good bef
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I think the simplest fix would be to assign a fixed usesysid of 1.
Slightly more flexible: make the ID number an initdb option, with a
default of 1. This would let people do it the old way if they wanted.
Doesn't seem very critical though.
Hi Peter,
Any idea of how many "extra memory moving operations" that would be?
:-)
Regards and best wishes,
Justin Clift
Peter Eisentraut wrote:
>
> It occurred to me that a server with locale features that is started in
> the C locale is going to behave the same as a server without locale
It occurred to me that a server with locale features that is started in
the C locale is going to behave the same as a server without locale
features. The exception are a few extra memory moving operations. (I
sincerely hope that all systems' libcs have optimized paths for the C
locale.) So we c
On Sun, 19 Aug 2001, Tom Lane wrote:
> One thing that I find absolutely essential for dealing with any large
> project is a full-text indexer (I use Glimpse, but I think there are
> others out there). Being able to quickly look at every use of a
> particular identifier goes a long way towards ans
We've had some problem reports that the current practice of initdb
assigning to the postgres user the same usesysid as the user id of the
Unix user running initdb has caused some clashes.
(Imagine this scenario: A few years ago you installed BluePants Linux
5.0, created a user for PostgreSQL, id
"Serguei Mokhov" <[EMAIL PROTECTED]> writes:
> And what's wrong in automated guide generation?
Even more to the point, what's wrong with looking at the source code?
(Why would you want a "line by line" guide if you're not looking at the
source code, anyway?)
We could probably do with more extens
mlw wrote:
>
> Just a suggestion, how much work would it be to accept multiple parameters on
> aggregate functions?
>
> For instance:
>
> select fubar(field1, field2) from table one group by field1;
>
> The reason I think that this is useful is that for some statistical operations,
> often tim
- Original Message -
From: Gavin Sherry <[EMAIL PROTECTED]>
Sent: Sunday, August 19, 2001 3:40 AM
> Hi all,
>
> For a few months now I've been thinking about whether or not a guide
> ('line-by-line') to the Postgres source tree would be of any value.
[snip]
> So, what do people th
> > 4) Encoding "official" names are inconsistent. Here are my suggested
> >changes (referring http://www.iana.org/assignments/character-sets,
> >according to Peter's suggestiuon):
> >
> > ALT -> IBM866
> > KOI8 -> KOI8_R
> > UNICODE -> UTF_8 (Peter's suggestion)
> >
>
>
> > ALT -> IBM866
>
> Just a quick comment: ALT is not necessarily IBM866.
> It can be any US-ASCII or 26-character-alphabet Latin set, for example
> IBM819 or ISO8859-1. Is actually quite different from IBM866 in its
> true meaning, and they shouldn't be aliased together. ALT is used for ex
On Sun, Aug 19, 2001 at 11:02:57AM +0900, Tatsuo Ishii wrote:
> 4) Encoding "official" names are inconsistent. Here are my suggested
>changes (referring http://www.iana.org/assignments/character-sets,
>according to Peter's suggestiuon):
>
> ALT -> IBM866
> KOI8 -> KOI8_R
> UN
Tom Lane writes:
> But the LIKE code does know about multibyte character sets. Is it safe
> to assume that memcmp-based sorting will not make any mistakes with
> multibyte characters?
Remember that this memcmp-based sorting is the same sorting that texteq
will do when locale is turned off. So
Hiroshi Inoue writes:
> Hmm * string1 = string2 * doesn't imply * string1 LIKE string2 * ?
In the current implementation of LIKE, you're right. The SQL standard
allows for the possibility that "[d]epending on the collating sequence,
two strings may compare as equal even if they are of differen
> -Original Message-
> From: Peter Eisentraut
>
> Hiroshi Inoue writes:
>
> > Please look at my first question.
> >This depends on the assumption that '=' is equivalent in
> >any locale. Is it guaranteed ?
> >For example, ( 'a' = 'A' ) isn't allowed in any locale ?.
> >
> > And
Hi all,
For a few months now I've been thinking about whether or not a guide
('line-by-line') to the Postgres source tree would be of any value.
Such a guide would, most probably, trace an 'ultimate' query (ie,
one which requires the use of all source level functionality) through the
source as
23 matches
Mail list logo
