Only concurrent indexes in PostgreSQL

postgresqlprismasupabasedrizzlemigrations
When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:

Install this rule for wispbit

Add this rule to wispbit and it will run when you open a pull request

Install this rule for Coderabbit

Copy the configuration below and add it to your repository as .coderabbit.yml in your project root.

reviews:
  path_instructions:
    - path: "*.sql"
      instructions: |
                
        When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
        
        Bad:
        
        ```sql
        CREATE INDEX idx_users_email ON users(email);
        ```
        
        Good:
        
        ```sql
        CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
        ```

Install this rule for Greptile

Greptile rules can be added through the web interface. Please see this documentation for details on how to add custom rules and context.

When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:
```sql
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
```

File Path Patterns:

*.sql

Install this rule for GitHub Copilot

Copilot instructions can be added through the interface. See the documentation for details on how to create coding guidelines.

When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:
```sql
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
```

File Path Patterns:

*.sql

Install this rule for Graphite Diamond

Diamond custom rules can be added through the interface. See the documentation for details on how to create custom rules.

When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:
```sql
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
```

File Path Patterns:

*.sql

Use with Cline

Copy the rule below and ask Cline to review your code using this rule

When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:
```sql
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
```

Use with OpenAI Codex

Copy the rule below and ask OpenAI Codex to review your code using this rule

When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:
```sql
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
```

Use with Cursor

Copy the rule below and ask Cursor to review your code using this rule

When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:
```sql
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
```

Use with Claude Code

Copy the rule below and ask Claude Code to review your code using this rule

When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:
```sql
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
```

Install this rule for Windsurf

To set up rules for Windsurf Reviews, please see this documentation 

When creating indexes in PostgreSQL, always use the `CONCURRENTLY` option to prevent blocking writes during index creation.
Bad:
```sql
CREATE INDEX idx_users_email ON users(email);
```
Good:
```sql
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
```