Sorry for the multiple replies-to-self, but this seemed worth
specifically noting: the expansion also results in multiple calls to
tuple-returning functions, even functions marked VOLATILE. For example:
CREATE OR REPLACE FUNCTION expandtest(INTEGER) RETURNS test AS $$
DECLARE
rec test;
BEGIN
> This may be simplified to the comparison between these two queries:
... or even further into:
CREATE TYPE test AS ( a integer, b integer, c integer, d integer );
EXPLAIN SELECT ((SELECT ROW(1,1,1,1)::test)::test);
EXPLAIN SELECT ((SELECT ROW(1,1,1,1)::test)::test).*;
craig=# EXPLAIN SELECT (
On 13/11/2009 7:25 PM, Oleg Serov wrote:
> EXPLAIN ANALYZE SELECT ((SELECT tmp::test FROM (SELECT * FROM test
> LIMIT 1) tmp)::test).*;
This may be simplified to the comparison between these two queries:
SELECT ((SELECT test FROM test LIMIT 1)::test);
SELECT ((SELECT test FROM test LIMIT 1)::tes
On Fri, Nov 13, 2009 at 9:50 PM, Robert Haas wrote:
> On Fri, Nov 13, 2009 at 8:52 PM, obelich wrote:
>
> > Hi we want to report a problem in the instalation with .bin file in
> Opensuse
> > 11.2 this one give send a message problem, then dont install the daemon
> to
> > start PostgreSQL service
On Fri, Nov 13, 2009 at 8:52 PM, obelich wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5186
> Logged by: obelich
> Email address: obel...@gmail.com
> PostgreSQL version: 8.4.1
> Operating system: Opensuse 11.2
> Description: Not install daemon
On Fri, Nov 13, 2009 at 10:39 AM, Heikki Linnakangas
wrote:
> Tom Lane wrote:
>> Robert Haas writes:
>>> I think it would be over the top to suggest that pg_dump has to cope
>>> with modifications that can only occur through manual updates to the
>>> system catalogs, but it seems like anything th
The following bug has been logged online:
Bug reference: 5186
Logged by: obelich
Email address: obel...@gmail.com
PostgreSQL version: 8.4.1
Operating system: Opensuse 11.2
Description:Not install daemon
Details:
Hi we want to report a problem in the instalation with
Tom Lane wrote:
It might be nice if manual changes to system objects got dumped,
but that's really an AI-complete problem --- which properties of
the objects represent manual changes, and how can we know whether
trying to apply those changes to a new system version will work?
A diff against te
Tom Lane wrote:
> Robert Haas writes:
>> I think it would be over the top to suggest that pg_dump has to cope
>> with modifications that can only occur through manual updates to the
>> system catalogs, but it seems like anything that can be done using DDL
>> statements should be handled.
>
> Like
Robert Haas writes:
> I think it would be over the top to suggest that pg_dump has to cope
> with modifications that can only occur through manual updates to the
> system catalogs, but it seems like anything that can be done using DDL
> statements should be handled.
Like, say, DELETE FROM pg_proc
On Fri, Nov 13, 2009 at 1:13 AM, Tom Lane wrote:
> "Robert Haas" writes:
>> The following command does not change the output of "pg_dumpall":
>> alter tablespace pg_default owner to bob;
>
> I don't think this is a bug. It's one specific aspect of a general
> principle that system objects don't
SQL:
CREATE TABLE test (id BIGINT, id2 BIGINT, id3 BIGINT, id4 BIGINT);
INSERT INTO test SELECT i, i, i, i FROM generate_series(0, 9) i;
EXPLAIN ANALYZE SELECT ((SELECT tmp::test FROM (SELECT * FROM test
LIMIT 1) tmp)::test).*;
WILL:
QUERY PLAN
Result (cost=0.11..0.12 rows=1 width=0) (actual time
Thank you, fixed.
We are using btree_gin module. I've created multicolumn gin indexes on table
with one column type tsvector and other column type integer. After index
creation selects works well. But after inserting new rows inserted row
appears in selects even when it does not satisfy conditio
Siwat Siwarborvorn wrote:
> - postgresql 8.3.1 compile with options
Although there isn't anything that might explain this issue, you should
upgrade to the latest 8.3 minor release.
> 6) Every time we fixe by reindex pg_proc_proname_args_nsp_index.
Did you keep a copy of the data files? What do
Will see
Tom Lane wrote:
"Yury Don" writes:
mdb=# create table tmp (id integer not null primary key, t tsvector, i
integer);
CREATE TABLE
mdb=# insert into tmp values (1, 'word', 66);
INSERT 0 1
mdb=# create index tmp_idx on tmp using gin (t, i);
CREATE INDEX
mdb=# insert into tmp values (2, '
The following bug has been logged online:
Bug reference: 5185
Logged by: Siwat Siwarborvorn
Email address: pg-supp...@xsidekick.com
PostgreSQL version: 8.3.1
Operating system: Aix 5.3 64bit
Description:postgres error "invalid page header in block xx of
relation "pg_pr
16 matches
Mail list logo
