Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Thanks. I'll make the migration fail on this condition more softly, by disabling the full text search in such cases. The problem is that triggers for the full text indexing are written in plpgsql procedural language that needs to be created in your database.

In postgres version <= 8.2 you do need to be a superuser to run that command. On versions >= 8.3 database can be configured so that database owner can run it.

Thanks. It depends on the version of postrges and how the admins had configured it. I've written the full text trigger code using version 8.3 manual.

In postgres <= 8.2 you do need to be a superuser to run that command and you may have additional problems running the trigger setup that is applied later in the same migration.

On versions >= 8.3 database can be configured so that database owner can run it.

I'll make the migration fail on this condition more softly, by disabling the full text search in such cases. The problem is that triggers for the full text indexing are written in plpgsql procedural language that needs to be created in your database.

In postgres version <= 8.2 you do need to be a superuser to run that command. On versions >= 8.3 database can be configured so that database owner can run it.

It depends on the version of postrges and how the admins had configured it. I've written the full text trigger code using version 8.3 manual.

In postgres <= 8.2 you do need to be a superuser to run that command and you may have additional problems running the trigger setup that is applied later in the same migration.

On versions >= 8.3 database can be configured so that database owner can run it.

If do not have access to postgres 8.3 and higher, then it might be easier for you to use MySQL.

I'll make the migration fail on this condition more softly, by disabling the full text search in such cases. The problem is that triggers for the full text indexing are written in plpgsql procedural language that needs to be created in your database.

It depends on the version of postrges and how the admins had configured it. I've written the full text trigger code using version 8.3 manual.it.

In postgres <= 8.2 you do need to be a superuser to run that command and you may have additional problems running the trigger setup that is applied later in the same migration. I've written the full text trigger code using version 8.3 manual.

On versions >= 8.3 database can be configured so that database owner can run it.

If do not have access to postgres 8.3 and higher, then it might be easier for you to use MySQL.

I'll make the migration fail on this condition more softly, by disabling the full text search in such cases. The problem is that triggers for the full text indexing are written in plpgsql procedural language that needs to be created in your database.

It depends on the version of postrges and how the admins had configured it.

In postgres <= 8.2 you do need to be a superuser to run that command and you may have additional problems running the trigger setup that is applied later in the same migration. I've written the full text trigger code using version 8.3 manual.

On versions >= 8.3 database can be configured so that database owner can run it, the default setting allows it.

If do not have access to postgres 8.3 and higher, then it might be easier for you to use MySQL.

I'll make the migration fail on this condition more softly, by disabling the full text search in such cases. The problem is that triggers for the full text indexing are written in plpgsql procedural language that needs to be created in your database.