Tom Lane wrote:
I've built applications that do roughly this sort of thing in Postgres
(some of the protocol changes in 6.4 were done to make it easier ;-)).
I may misremember, but IIRC some older protocol (or at least libpq)
returned 0 as backend pid to listening client if it was notified
Christopher Kings-Lynne kirjutas R, 07.03.2003 kell 07:28:
Yeah, it's not really a problem for me, I just put the extra clause in.
Is indexing excluding NULLs a common application of partial indexes?
For me it is ;)
It's
basically all I use it for, when a column has like 90-95% NULLS and
mlw kirjutas E, 31.03.2003 kell 03:43:
Given a HTTP formatted query:
GET http://localhost:8181/pgmuze?query=select+*+from+zsong+limit+2;
The output is entered below.
Questions:
Is there a way, without spcifying a binary cursor, to get the data types
associated with columns? Right now I
[EMAIL PROTECTED] kirjutas E, 31.03.2003 kell 19:52:
Actually, as far as I am aware, the header is for metadata, i.e. it is the
place to describe the data being returned.
Did you read the SOAP spec ?
The description of the fields
isn't the actual data retrieved, so it doesn't belong in the
mlw kirjutas T, 01.04.2003 kell 15:29:
Hannu Krosing wrote:
[EMAIL PROTECTED] kirjutas E, 31.03.2003 kell 19:52:
Actually, as far as I am aware, the header is for metadata, i.e. it is the
place to describe the data being returned.
Did you read the SOAP spec ?
yes
mlw kirjutas K, 02.04.2003 kell 15:56:
Hannu Krosing wrote:
What you have come up with _is_not_ a SOAP v1.1 message at all. It does
use some elements with similar names but from different namespace.
the SOAP Envelope, Header and Body elemants must be from namespace
http
[EMAIL PROTECTED] kirjutas N, 03.04.2003 kell 02:01:
mlw wrote:
I think you are interpreting the spec a bit too restrictively. The
syntax is fairly rigid, but the spec has a great degree of flexibility.
I agree that, syntactically, it must work through a parser, but there is
lots of
Hiroshi Inoue kirjutas E, 31.03.2003 kell 03:40:
Tom Lane wrote:
Serializable or not, there is a good case for saying that cursors don't
see changes made after they are opened, period. The current
implementation locks down the cursor's snapshot at DECLARE time.
It's only because
Hiroshi Inoue kirjutas E, 31.03.2003 kell 19:08:
-Original Message-
From: Hannu Krosing [mailto:[EMAIL PROTECTED]
Hiroshi Inoue kirjutas E, 31.03.2003 kell 03:40:
2) dynamic
It can detect any changes made to the membership, order,
and values of the result set
The Hermit Hacker kirjutas R, 20.06.2003 kell 08:28:
On Fri, 20 Jun 2003, Tom Lane wrote:
On Fri, 20 Jun 2003, The Hermit Hacker wrote:
Is there a strong reason why tsearch isn't in gborg?
I think text search is a pretty important facility that should
eventually be part of the core
Tom Lane kirjutas E, 23.06.2003 kell 01:29:
Kevin Jacobs [EMAIL PROTECTED] writes:
Attached is a patch that removes all of the RExec code from plpython from
the current PostgreSQL CVS. In addition, plpython needs to be changed to an
untrusted language in createlang.
I am inclined to
Tom Lane kirjutas E, 30.06.2003 kell 00:18:
Hannu Krosing [EMAIL PROTECTED] writes:
could we not just make sure that plpython uses python ver 2.x and use
plpythonu for python versions = 2.x until a secure regex solution comes
from Guido and folks ?
We'd still have to mark it untrusted
Tom Lane kirjutas E, 30.06.2003 kell 01:21:
Hannu Krosing [EMAIL PROTECTED] writes:
The version with patch which removes RExec (as Python 2.x is not
supporting it ) is the right thoing to do FOR PYTHON 2.X, but there is
no reason to remove safe execution when using python 1.5.x.
Who's
Tom Lane kirjutas E, 30.06.2003 kell 06:39:
Hannu Krosing [EMAIL PROTECTED] writes:
Tom Lane kirjutas E, 30.06.2003 kell 01:21:
Who's still using 1.5, I guess is the question? And are they likely
to be updating their PG installation when they're not updating Python?
I guess that anyone
elein kirjutas T, 24.06.2003 kell 00:42:
There is a realtively clean hack one can use to convert plpython
functions to plpythonu manually - just rename the language for the time
of loading functions - do as superuser
update pg_language set lanname = 'plpython' where lanname = 'plpythonu';
LOAD
Oleg Bartunov kirjutas T, 01.07.2003 kell 15:49:
Hi there,
attached archive contains simple parser demonstrating our
problem. untar it, make, make test
Good test:
echo -n 12 34.1234 ... | ./parser
INTEGER:'12'
CHAR: ' '
VERSION:'34.1234'
CHAR: ' '
DOT:'.'
Oleg Bartunov kirjutas K, 02.07.2003 kell 11:39:
The problem is recognizing VERSION
(from gram.y)
version:
INTEGER DOT INTEGER{ $$ = strconcat($1, $3, $2); }
| version DOT INTEGER { $$ = strconcat($1, $3, $2); }
removing the line above seems to fix your
WHen running PostgreSQL 7.3.3-1 (from rpm's) on Redhat 9.0 I got the
following in logs and the postmaster will not start up.
Any Ideas what I could do to start up ?
This in on a laptop used for development, but I still would like to not
initdb.
postmaster successfully started
LOG: database
Tom Lane kirjutas N, 17.07.2003 kell 19:49:
Ugh. The reason we hadn't seen this happen in the field was that it is
a bug I introduced in a patch two months ago :-(
7.3.3 will in fact fail to start up, with the above error, any time the
last record of the WAL file ends exactly at a page
Tom Lane kirjutas R, 08.08.2003 kell 16:56:
Bruce Momjian [EMAIL PROTECTED] writes:
o Add optional textual message to NOTIFY
Not done, but there is room in the FE/BE protocol now for something like
this.
Were there any other changes to NOTIFY - there was talk about making
NOTIFY
Christopher Kings-Lynne kirjutas N, 07.08.2003 kell 04:33:
My other question is we play around with bytea fields to escape nulls and
chars 32 and stuff so that when someone browses the table, they get
'\000unknown\000...', etc.
actually bytea *stores* char(0), you get \000 or \x0 or @ or
Rahul_Iyer kirjutas K, 13.08.2003 kell 08:23:
hi...
im on a project using Postgres. The project involves, at times, upto
5,000,000 inserts. I was checking the performance of Postgres for 5M inserts
into a 2 column table (one col=integer, 2nd col=character). I used the
Prepare... and execute
Oleg Bartunov kirjutas E, 11.08.2003 kell 11:52:
On Mon, 11 Aug 2003, Peter Eisentraut wrote:
Alexey Mahotkin writes:
AFAIK, currently the codepoints are sorted in their numerical order. I've
searched the source code and could not find the actual place where this is
done. I've
Joe Conway kirjutas N, 28.08.2003 kell 21:15:
Greg Stark wrote:
Specifically I want to know how to replace my int_array_aggregate(int) and
int_array_enum(_int) calls.
I have no idea what those are -- are they from contrib?
You can create an aggregate to turn arbitrary datatype elements
Rod Taylor kirjutas R, 29.08.2003 kell 03:31:
I've been fiddling away on ALTER TABLE and have a few questions about a
possible datatype change. Just alter portions.
I presume I'll need to do a table rewrite. What is the best way to
change a single datum? heap_modify() takes a single
Tom Lane kirjutas E, 01.09.2003 kell 15:41:
Bruce Momjian [EMAIL PROTECTED] writes:
I know someone reported a problem with the hash indexes (data loss,
serious)--- was that a new 7.4 but or something that has existed for a
long time?
AFAICT the bug's been there since Berkeley days.
One
Joerg Hessdoerfer kirjutas N, 04.09.2003 kell 10:22:
I'm currently in the process of setting up my development environment (how the
heck do I get bison/flex to compile under MingW/MSYS? Oh my...)
there is a precompiled bison in the MinGW filelist
http://www.mingw.org/download.shtml#hdr2
dunno
Andrew Dunstan kirjutas L, 06.09.2003 kell 16:14:
Peter Eisentraut wrote:
Tom Lane writes:
There are good security arguments not to have it in the default install,
no?
I think last time the only reason we saw was that dump restoring would be
difficult. I don't see any
Heikki Tuuri kirjutas P, 21.09.2003 kell 12:51:
Tom,
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, September 21, 2003 10:32 AM
Subject: Re: [HACKERS] PostgreSQL not ACID compliant?
Heikki Tuuri
Andreas Pflug kirjutas E, 29.09.2003 kell 12:04:
Christopher Kings-Lynne wrote:
You could just as easily argue that the lack of integrity testing at
data load time was equally a bug.
I think we need someway of telling postgres to suppress a foreign key
check.
The main problem is
Shridhar Daithankar kirjutas E, 29.09.2003 kell 13:34:
On Monday 29 September 2003 15:58, Christopher Kings-Lynne wrote:
So a db designer made a bloody mistake.
The problem is there's no easy way to find out what's missing.
I'd really like EXPLAIN to display all subsequent triggered queries
Bruce Momjian kirjutas T, 30.09.2003 kell 02:16:
Tom Lane wrote:
! Faster regular expression code
We could tout more functionality too, since the new regex package
has a lot of advanced stuff that wasn't there before.
Added more powerful
This wording covers nicely
Tom Lane kirjutas N, 02.10.2003 kell 17:30:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
What is going on here? Surely getting a FOR UPDATE row lock should
prevent another process getting an update lock?
The behavior you describe would certainly be a bug, but you'll have to
show a
James Rogers kirjutas N, 02.10.2003 kell 20:50:
To give a real world example, a standard query on one of our tables that
has not been CLUSTER-ed recently (i.e. within the last several days)
generates an average of ~2,000 cache misses. Recently CLUSTER-ed, it
generates ~0 cache misses on
James Rogers kirjutas N, 02.10.2003 kell 23:44:
On Thu, 2003-10-02 at 12:09, Hannu Krosing wrote:
So what you really need is the CLUSTER command to leave pages half-empty
and the tuple placement logic on inserts/updates to place new tuples
near the place where they would be placed
Mike Mascari kirjutas L, 04.10.2003 kell 06:32:
2) The query language should be computationally complete. The user
should be able to author complete applications in the language, rather
than the language being a sublanguage.
To me it seems like requiring that one should be able to author
Tom Lane kirjutas R, 03.10.2003 kell 18:34:
Michael Brusser [EMAIL PROTECTED] writes:
But when I doubled the number of backslashes:
SELECT smth. FROM tbl WHERE situation LIKE '%%';
- it actually worked fine.
Backslash is special to both the string-literal parser and the LIKE code.
Christopher Browne kirjutas R, 03.10.2003 kell 00:57:
[EMAIL PROTECTED] (Jean-Luc Lachance) writes:
That's one of the draw back of MVCC.
I once suggested that the transaction number and other house keeping
info be included in the index, but was told to forget it...
It would solve once
Tom Lane kirjutas L, 04.10.2003 kell 19:07:
Hannu Krosing [EMAIL PROTECTED] writes:
Christopher Browne kirjutas R, 03.10.2003 kell 00:57:
A while back I outlined how this would have to be done, and for it to
be done efficiently, it would be anything BUT simple.
Could this be made
Greg Stark kirjutas P, 05.10.2003 kell 00:17:
I've never seen anyone use this feature, and I never seriously considered it
myself. It sort of has the feel of an antiquated feature that traded too much
flexibility and abstraction for raw performance on very slow disk hardware.
Read A
James Rogers kirjutas T, 07.10.2003 kell 01:48:
Hi,
I guess what I am wondering
is whether there is any kind of quasi-official mechanism for putting
certain features in certain future versions depending on the nature and
significance of implementing those features and the number of things
Jean-Michel POURE kirjutas E, 13.10.2003 kell 16:20:
Le Lundi 13 Octobre 2003 14:45, Robert Treat a crit :
Someone could have downloaded the package from sourceforge/freshmeat, so
I don't think it hurts to have a pointer to postgresql.org. What might
be better than a link for the submit
James Rogers kirjutas K, 15.10.2003 kell 11:26:
On 10/14/03 11:31 PM, James Rogers [EMAIL PROTECTED] wrote:
There is some abstraction in Postgres and the database is well-written, but
it isn't written in a manner that makes it easy to swap out operating system
or API models. It is
Tom Lane kirjutas E, 20.10.2003 kell 03:35:
Oliver Elphick [EMAIL PROTECTED] writes:
There is a bug in Unicode upper() which has been present since 7.2:
We don't support upper/lower in multibyte character sets, and can't as
long as the functionality is dependent on ctype.h's
Tatsuo Ishii kirjutas E, 20.10.2003 kell 15:37:
Tom Lane kirjutas E, 20.10.2003 kell 03:35:
Oliver Elphick [EMAIL PROTECTED] writes:
There is a bug in Unicode upper() which has been present since 7.2:
We don't support upper/lower in multibyte character sets, and can't as
long as
Peter Eisentraut kirjutas E, 20.10.2003 kell 21:02:
Tom Lane writes:
I noticed by chance that glibc has a reentrant locale API that seems
to allow for efficient access to multiple locales concurrently. Perhaps
it would be a reasonable solution to support multiple locales only on
Karel Zak kirjutas T, 21.10.2003 kell 10:50:
On Mon, Oct 20, 2003 at 10:58:00PM +0200, Peter Eisentraut wrote:
(Note that I say Unicode a lot here because those people do a lot of
research and standardization in this area, which is available for free,
but this does not constrain the
Tatsuo Ishii kirjutas T, 21.10.2003 kell 12:07:
Why cannot do PostgreSQL as 100% pure Unicode system? We can do
conversion from/to others encodings as client/server communication
extension, but internaly in BE we can use only pure Unicode data. I
think a lot of things
Anthony W. Youngman kirjutas P, 19.10.2003 kell 21:24:
As soon as a requirement for a database specifies extraction of the
maximum power from the box, it OUGHT to rule out all the current
relational databases. MV flattens it for it for performance. As an MV
programmer, I *KNOW* that I can
Marshall Spight kirjutas N, 23.10.2003 kell 11:01:
Anthony W. Youngman [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]
Just like the academics were
brainwashed into thinking that microkernels were the be-all and end-all
- until Linus showed them by practical example that they were
Peter Eisentraut kirjutas R, 24.10.2003 kell 22:16:
Jochen Westland [invigo] writes:
In my version
select round(2.5); returns 2;
select round(2.501) returns 3;
refering to my math professor thats wrong, at least in germany.
select round(2.5); should return 3
The convention
Eduardo D Piovesam kirjutas E, 20.10.2003 kell 16:35:
They stopped at 7.2.4 because they're finishing some usefull APIs,
which'll make the port much more easy.
Will this involve using a Linux kernel ;)
When this part is done, a new port will be made with 7.4. With much
less NetWare specific
Dennis Bjorklund kirjutas P, 26.10.2003 kell 07:30:
On Sat, 25 Oct 2003, Joe Conway wrote:
That will modify the bytea column so that it is stored uncompressed in
the TOAST table.
Now, simply use substr() to grab any random chunk:
SELECT substr(foo_bytea, 2, 100) from foo where
Tom Lane kirjutas P, 02.11.2003 kell 20:00:
Jan Wieck [EMAIL PROTECTED] writes:
I am currently looking at implementing ARC as a replacement strategy. I
don't have anything that works yet, so I can't really tell what the
result would be and it might turn out that we want both features.
it in.
Don't try to solve too many problems at once. Starting with just a
possibility to move suitable ready-made partitions in and out of
inheritance chain solves a really big problem. No need to try to
obfuscate it with extra functionality, at least not initially.
--
Hannu Krosing
are evil in case they cause some fast-changing table
to grow its storage size several orders of magnitude, but if that is not
the case then they just run there in backgroun with no ill effects,
especially do-nothing transactions like vacuum.
--
Hannu Krosing
Database Architect
Skype
.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 9: In versions below 8.0
old tuples,
but instead just marks them by setting xmin=xmax for them, in addition
to its freezing of live-and-visible-to-all tuples.
This would avoid touching indexes at all and may well be what is desired
for tables with only very little updates/deletes.
--
Hannu Krosing
Database
checking, just
comparison of metainfo. the partitions could be huge and having to check
data inside them would negate most of the usefullness for ADD/DROP
INHERITS.
--
Hannu Krosing
Database Architect
Skype Techshould benologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me
Ühel kenal päeval, N, 2006-06-08 kell 12:09, kirjutas Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
If the aim is to *only* avoid transaction wraparound, then maybe we
could introduce VACUUM FREEZE ONLY; which never removes any old tuples,
but instead just marks them by setting xmin
Ühel kenal päeval, N, 2006-06-08 kell 11:42, kirjutas Greg Stark:
Hannu Krosing [EMAIL PROTECTED] writes:
Do you mean that in newer versions ALTER TABLE ADD COLUMN will change
existing data without asking me ?
That would be evil!
Even worse if ALTER TABLE ALTER COLUMN SET DEFAULT
conislocal and coninh.
Currently pg_dump generates all constraints with ONLY clause anyway.
But I agree that we should get rid of ONLY for ADD CONSTRAINT once we
disallow dropping inherited constraints.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F
a
goal in itself.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 3: Have you
the cluster.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 2: Don't 'kill -9
IDLE or also IDLE in transaction ?
If we are going to change things anyway, I'd like the latter to show the
time since start of transaction, so that I Would at least have an easy
way to write a transaction timeout script :)
I don't really care about what plain IDLE uses.
--
Hannu
:)
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 5: don't forget to increase your
is setting up the server so that you
can service your loads comfortably. Running the server at 100% lead is
not anything you want to do on production server. There will be things
you need to do anyway and you need some headroom for that.
--
Hannu Krosing
Database Architect
Skype
.
Usually it gets really bad if you *don't* run vacuum continuously, maybe
hopeing to do it in slower times at night. For high-update db you have
to run it continuously, maybe having some 5-15 sec pauses between runs.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia
.
VACUUMing often also solves the problem of steady degradation of
performance between vacuums :)
No need to be afraid of vacuum. Vacuum is your friend! Just learn to use
it right.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
to disk by time of vacuum, so no additional traffic
there. If you had made 5 updates per page and then vacuum it, then you
make effectively 1 extra WAL write meaning 20% increase in WAL traffic.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn
by tuple deletion time,
and always cleaned up up to the oldest running transaction's start
time... there would be no need for any other autovacuum then.
This has been on todo list for some time already.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F
bit in an index leaf node causes
nearly as much disk io as removing the node.
If we could delete/reuse old index tuples, it would solve a sizable
chunk of index-growth problem, especially for cases where referenced key
value does not change.
--
Hannu Krosing
Database Architect
was to that imagined behaviour and thus
ignored all the real problems of such change.
All the next suggestions were variations of the first ones, and failed
to address or even research any problems brought up.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn
cases.
Another possible solution for indexes with mostly dead pointers is doing
a reindex, but this will become possible only after we have implemented
a concurrent, non-blocking CREATE INDEX.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn
Ühel kenal päeval, L, 2006-06-24 kell 19:36, kirjutas Bruce Momjian:
Hannu Krosing wrote:
?hel kenal p?eval, R, 2006-06-23 kell 13:08, kirjutas Tom Lane:
Bottom line: there's still lots of low-hanging fruit. Why are people
feeling that we need to abandon or massively complicate our
until they slow(ish)ly claim their own page.
Does that help explain it?
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end
, but this is not relevant to current
discussion).
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP
?
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please
some decent discussion about the problem did happen, and
that is good.
Agreed.
Maybe this _was_ the best way to bring up the discussion again.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get
Ühel kenal päeval, E, 2006-06-26 kell 10:50, kirjutas Bruce Momjian:
Hannu Krosing wrote:
?hel kenal p?eval, E, 2006-06-26 kell 14:56, kirjutas Martijn van
Oosterhout:
On Mon, Jun 26, 2006 at 07:17:31AM -0400, Bruce Momjian wrote:
Correct! We use the same pointers used by normal
that
gets tuple by its ctid must be able to trace forward chains within the
page.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
-updated tables avoid that, but there
may be still cases where this is needed.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
Ühel kenal päeval, T, 2006-06-27 kell 10:38, kirjutas Hannu Krosing:
Ühel kenal päeval, E, 2006-06-26 kell 23:08, kirjutas Bruce Momjian:
Jim C. Nasby wrote:
On Mon, Jun 26, 2006 at 02:32:59PM -0400, Bruce Momjian wrote:
It is certainly possible to do what you are suggesting
Ühel kenal päeval, E, 2006-06-26 kell 11:31, kirjutas Bruce Momjian:
Hannu Krosing wrote:
pass 3: clean heap based on ctid from pass 1
If yo do it this way, you dont need to invent new data structures to
pass extra info about CITC internals to passes 2 and 3
On more
. (VACUUM is safe against that because
it only holds one lock.)
Tom - what do you think of the other related idea, that of reusing dead
index entries ?
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get
Ühel kenal päeval, T, 2006-06-27 kell 12:16, kirjutas Bruce Momjian:
Hannu Krosing wrote:
?hel kenal p?eval, T, 2006-06-27 kell 10:38, kirjutas Hannu Krosing:
?hel kenal p?eval, E, 2006-06-26 kell 23:08, kirjutas Bruce Momjian:
Jim C. Nasby wrote:
On Mon, Jun 26, 2006 at 02:32:59PM
value.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 6: explain analyze
corrupting some backend/shared-mem structures ?
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast
on parent rownt fired a trigger that changes child table rows and there
rows fired another trigger that changed the same parent row again.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype
.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 1: if posting/reading through
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ
the minimum to 1% or even 0.1% and apply
similar logic you suggested for btree pages above, that is stop adding
new ones when the threasold is reached.
Comments?
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me
although workable,
has a bit of a house-of-cards feel to it sometimes.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end
this is.
It may become populat again, when we will be able to do index-only
scans.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end
at some API level.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 1: if posting
.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 9: In versions below 8.0
to have an easy way to retrieve and install the desired PL's
but that's more of a packaging issue.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get
;)
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 5: don't forget to increase your
of)
seconds.
Is anyone working on it ?
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP
801 - 900 of 1744 matches
Mail list logo
