btree entries - Search results in mailing lists
Mailing lists >> pgsql-sql >> Thread
2020-02-29 16:50:24 | min()/max() with BRIN indexes (Wayne)
entries are continuously added to the table with the current time. If I convert from BTREE
Mailing lists >> pgsql-sql >> Thread
2016-05-17 04:47:23 | Re: PostgreSQL:ALTER TABLE command hangs forever when DB partitioning is enabled. (Venkatesan, Sekhar)
entry | character varying(120) | | extended | | i_branch_cnt | integer | | plain | | i_direct_dsc | smallint | | plain | | r_immutable_flag | smallint | | plain | | r_frozen_flag | smallint | | plain | | r_has_events | smallint | | plain | | acl_domain | character varying
Mailing lists >> pgsql-sql >> Thread
2016-04-25 05:48:17 | Re: Re: PostgreSQL:ALTER TABLE command hangs forever when DB partitioning is enabled. (Venkatesan, Sekhar)
entry | character varying(120) | | extended | |i_branch_cnt | integer | | plain | |i_direct_dsc | smallint | | plain | |r_immutable_flag | smallint | | plain | |r_frozen_flag | smallint | | plain | |r_has_events | smallint | | plain | |acl_domain | character varying
Mailing lists >> pgsql-sql >> Thread
2014-12-14 09:18:01 | foregin table insert error (Ed Rahn)
btree (id) "cache_name_id_entry_id_key" UNIQUE CONSTRAINT, btree (name_id, entry_id) "ix_cache
Mailing lists >> pgsql-sql >> Thread >> Search in thread (2)
2011-08-31 18:27:38 | function based index problem (Viktor Bojović)
entry USING btree (length(sequence::text)); When using ">=" in search which returns only two records
Mailing lists >> pgsql-sql >> Thread >> Search in thread (2)
2009-07-09 15:33:26 | Re: FW: Query length limitation in postgres server > 8.2.9 ()
btree (leaf_category_1, site_id) WHERE leaf_category_1 IS NOT NULL If I were you I'd drop the WHERE clause, which is eliminating no index entries
Mailing lists >> pgsql-sql >> Thread
2008-09-02 19:29:52 | seemingly slow for-loop in plpgsql (Claus Guttesen)
entries were updated I found out that '\n' was added to the md5-checksum. :-) So I wanted to update the table using plpgsql. As I understand it from the docs (http:///docs/8.3/static/plpgsql-control-structures.html) in section
Mailing lists >> pgsql-sql >> Thread
2008-06-04 08:20:53 | Problems with a Query between 7.3 and 8.2 (Holm Tiffe)
entry for table "best_hdr"poid | prodort | anz | art | bez1 ------+----------------------+-----+-----+---------------------------------- 1 | VK-Kueche | 5 | 50 | Malzkaffee 1 | VK-Kueche | 30 | 57 | Kakao 1 | VK-Kueche | 18 | 58 | Milch warm ... The tables are as follows: Table
Mailing lists >> pgsql-sql >> Thread
2008-04-19 14:56:33 | Re: Desc Commnad in pgsql? (Christopher Browne)
entry_id_seq'::regclass) Indexes: "acc_trans_pkey" PRIMARY KEY, btree (entry_id) "acc_trans
Mailing lists >> pgsql-sql >> Thread
2007-08-10 18:30:27 | Re: Index usage in order by with multiple columns in order-by-clause (Tom Lane)
btree index isn't magic, it's just an ordered list of entries. So you can't just
Mailing lists >> pgsql-sql >> Thread
2006-11-19 02:41:30 | planner used functional index in 7.3.6, now does a seq scan in 7.4.7 after upgrade (Chris Tennant)
entry_id)Total runtime: 581.390 ms (13 rows) Here are the schema details for the table with the functional index: Table "public.opt_stereo_pair_image_attributes" Column | Type | Modifiers ------------------------------+-----------------------------+--------------------id | integer | not nullleft_patient
Mailing lists >> pgsql-sql >> Thread
2006-08-14 22:53:54 | Re: Using bitmap index scans-more efficient (Tom Lane)
btree has no idea about the constraint (that I imagine exists) that left <= right. If you're just doing a simple index on (left, right) then the above query requires scanning all index entries
Mailing lists >> pgsql-sql >> Thread
2006-04-17 14:29:36 | Truncate and Foreign Key References question (Gregory S. Williamson)
entries currently in my collections_l table. I need to wipe out the contents of the collections_l table nightly and refresh it from a remote master source. (Don't ask ... long & sordid history
Mailing lists >> pgsql-sql >> Thread
2005-11-22 13:50:46 | Re: can UNIQUEness of TEXT datatype really be guaranteed? (Tom Lane)
entry is too large to fit into a btree index entry (from memory, about 2700 bytes
Mailing lists >> pgsql-sql >> Thread
2005-03-21 04:12:14 | Group by 15 Minute Steps (Martin Knipper)
btree (id) Foreign-key constraints: "data_diff_device_fkey" FOREIGN KEY (device) REFERENCES device(id) ON UPDATE CASCADE ON DELETE CASCADE [...] An example query looks like this: snmp=# select snmpzeit as snmp,ifinoctets,ifoutoctets from