On Sun, Nov 17, 2013 at 10:48 PM, David Johnston wrote:
> I am preparing to REINDEX the unique index and DROP the non-unique one over
> the same field - probably Tuesday evening. Does everything I am saying here
> sound kosher or would someone like me to provide additional information?
[...]
>
On 11/17/2013 11:48 PM, David Johnston wrote:
> I am guessing that it is the need for the index to point to new versions of
> the physical record that the index is churning so much and causing this kind
> of bloat?
Bingo.
> I am preparing to REINDEX the unique index and DROP the non-unique one ov
Hi,
I have a table with the following usage characteristic:
INSERT bulk data using INSERT INTO ... SELECT ... FROM
-- this table uses a varchar(50) for the PK
-- the PK is rarely (effectively never unless a mistake was made) altered
-- always appending to the existing table; some bulk deletions i
On Tue, Oct 25, 2011 at 2:41 AM, Raghavendra
wrote:
> On Tue, Oct 25, 2011 at 11:40 AM, Manoj K P wrote:
>>
>> Server log Oct 1 00:06:59 server_host_name postgres[1453]: [5-1]
>> 2011-10-01 00:06:59.831 EDT 1453 4e869041.5ad postgres [local] postgres LOG:
>> duration: 418583.238 ms statement: sel
On Tue, Oct 25, 2011 at 11:40 AM, Manoj K P wrote:
> *Server log* Oct 1 00:06:59 server_host_name postgres[1453]: [5-1]
> 2011-10-01 00:06:59.831 EDT 1453 4e869041.5ad postgres [local] postgres LOG:
> duration: 418583.238 ms statement: select pg_start_backup('fortnightly');
> Oct 2 03:03:18 serve
*Server log*
Oct 1 00:06:59 server_host_name postgres[1453]: [5-1] 2011-10-01
00:06:59.831 EDT 1453 4e869041.5ad postgres [local] postgres LOG: duration:
418583.238 ms statement: select pg_start_backup('fortnightly');
Oct 2 03:03:18 server_host_name postgres[1453]: [6-1] 2011-10-02
03:03:18.2
On Mon, Oct 24, 2011 at 3:22 AM, Manoj K P wrote:
> Postgres recovered from data folder , after that some queries shows error
>
>
> select * from table2 order by app_id ; - its work ( 5000 data)
> select * from table2 order by app_id desc ; - its work
>
> Here app_id contains binary index
On Mon, Oct 24, 2011 at 8:32 AM, manoj wrote:
> On 10/24/2011 06:38 PM, Merlin Moncure wrote:
>
> On Mon, Oct 24, 2011 at 3:22 AM, Manoj K P wrote:
>
> Postgres recovered from data folder , after that some queries shows error
>
>
> select * from table2 order by app_id ; - its work ( 5000 dat
On 10/24/2011 06:38 PM, Merlin Moncure wrote:
On Mon, Oct 24, 2011 at 3:22 AM, Manoj K P wrote:
Postgres recovered from data folder , after that some queries shows error
select * from table2 order by app_id ; - its work ( 5000 data)
select * from table2 order by app_id desc ; - its wor
Postgres recovered from data folder , after that some queries shows error
select * from table2 order by app_id ; - its work ( 5000 data)
select * from table2 order by app_id desc ; - its work
Here app_id contains binary index
select * from table2 order by id ; - its work ( 5000
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Really?
toll_archive=# create table snaggle (
toll_archive(# foo integer,
toll_archive(# bar integer,
toll_archive(# primary key (foo));
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"snaggle_pkey" for table "snaggle"
CREATE TABLE
Tim
2007/5/14, Sim Zacks <[EMAIL PROTECTED]>:
I read the section on indexes where it says that PostGreSQL creates a unique
index, but I didn't see an index on the table so I didn't know if it was
implicit or if
for some reason my primary keys weren't becoming indexes.
You are supposed to see thos
It is mixture of looking and knowing where to look. I read the section on indexes where it says that
PostGreSQL creates a unique index, but I didn't see an index on the table so I didn't know if it was
implicit or if for some reason my primary keys weren't becoming indexes. I didn't see the creat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/14/07 03:27, Sim Zacks wrote:
> Is a primary key an implicit index, or if I want to join on that field
> is it also worthwhile to make an explicit index?
On-line documentation is such a wonderful resource...
http://www.postgresql.org/docs/7.3/i
Is a primary key an implicit index, or if I want to join on that field is it also worthwhile to make
an explicit index?
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
15 matches
Mail list logo
