This is what we did:
0. BEGIN;
1. ALTER TABLE ... SET WITHOUT OIDS
2. A bunch of things are selected out of this table and inserted into
another (using INSERT ... SELECT)
3. An index is created on a timestamp field on this table
4. Then there's an update on a related table, that selects
On Wed, 21 Jan 2004, Christopher Kings-Lynne wrote:
This seems to be reproducible...
Here is a smaller example that show the problem:
CREATE TABLE foo (a INT);
BEGIN;
ALTER TABLE foo SET WITHOUT OIDS;
INSERT INTO foo values (5);
ROLLBACK;
VACUUM FULL foo;
It's easy to guess what is
On Wed, 21 Jan 2004, Christopher Kings-Lynne wrote:
This is what we did:
0. BEGIN;
1. ALTER TABLE ... SET WITHOUT OIDS
12. ROLLBACK;
13. VACUUM FULL forums_posts;
The problem here is that this conditional doesn't take into account the
change in state which the above transaction causes:
On Wed, 21 Jan 2004, Gavin Sherry wrote:
On Wed, 21 Jan 2004, Christopher Kings-Lynne wrote:
This is what we did:
0. BEGIN;
1. ALTER TABLE ... SET WITHOUT OIDS
12. ROLLBACK;
13. VACUUM FULL forums_posts;
The problem here is that this conditional doesn't take into account the
What's the actual distribution of values in these columns?
Are you searching for values that are particularly common
or uncommon?
This column always has a predefined set of values.
Usually the app. would search for one of the
existing values.
---
Total records:
On Wed, 21 Jan 2004, Michael Brusser wrote:
So 'rows' values are incorrect.
You can increase the statistics-gathering for that column with ALTER TABLE
and probably get better estimates.
Also looking at queries with 'KnowledgeBase'
and 'OtherParam' - does seq. scan make sense?
I mean
Tom Lane [EMAIL PROTECTED] writes:
Brian Moore [EMAIL PROTECTED] writes:
i would like to begin work on the TODO item
Allow backend to output result sets in XML
I am not sure why it's phrased that way --- surely the code to hack on
is the client side, not the backend. Otherwise you
Greg Stark wrote:
Personally I don't see any point in xml, but if there was a standard
query
protocol then a client could send queries to any database that
supported
it
without using any libraries. That might be useful. Of course you could
do
that
without xml, but people seem to get more
Greg Stark wrote:
Tom Lane [EMAIL PROTECTED] writes:
Brian Moore [EMAIL PROTECTED] writes:
i would like to begin work on the TODO item
Allow backend to output result sets in XML
I am not sure why it's phrased that way --- surely the code to hack
Michael Brusser [EMAIL PROTECTED] writes:
So 'rows' values are incorrect.
You sound like you are expecting them to be exact. They're just
estimates. They're all plenty close enough for planning purposes,
except maybe the one for 'KnowledgeBase' is a little further off
than I would have
Please forgive me if this is silly, but if you wanted XML from the server,
couldn't you just write a PL/Perl untrusted function that takes a SELECT
statement as its parameter, and returns a single scalar containing the XML?
- The XML:: modules in Perl help with the XML formatting
- DBD::PgSPI
Tom Lane wrote:
Brian Moore [EMAIL PROTECTED] writes:
i would like to begin work on the TODO item
Allow backend to output result sets in XML
I am not sure why it's phrased that way --- surely the code to hack
on is the client side, not the backend. Otherwise you need a
protocol
we lost a mail relay, so teseting to make sure configuration is still
working after replacing it with other local machines we have more contrl
over ...
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy
Peter Eisentraut wrote:
I think output XML is just buzz. Give us a real use scenario and an
indication that a majority also has that use scenario (vs. the other
ones listed above), then we can talk.
Consider:
create table person (name varchar primary key, age int);
create table account
The crash I'm getting can be boiled down to this:
regression=# create table fooey(f1 int) without oids;
CREATE TABLE
regression=# insert into fooey values(11);
INSERT 0 1
regression=# create temp table fooey2 as select distinct * from fooey;
server closed the connection unexpectedly
This
Tom Lane wrote:
The crash I'm getting can be boiled down to this:
regression=# create table fooey(f1 int) without oids;
CREATE TABLE
regression=# insert into fooey values(11);
INSERT 0 1
regression=# create temp table fooey2 as select distinct * from fooey;
server closed the connection
16 matches
Mail list logo
