You're better of changing your schema: if your id's are numbers, use
create table users(
id serial not null primary_key
-- other fields
);
and add a followers table that contains one row per follower:
create table followers (
user_id int not null references users(id),
follower_id int not null references users(id),
unique (user_id, follower_id)
);
and then you can simply select the followers for user with id X like this:
select * from users
where id in (select follower_id from followers where user_id = X)
Relational databases are very good at managing relationships, but you have to use the functionality that they provide for this: tables, rows, foreign keys, and indexes.
It is typically bad practice to store lists of ID's in a column, because that requires special code to split such a text column up into separate ID's. This code must be run for every row in your resultset, slowing things down enormously.
PostgreSQL does have extensive support for array columns, but not all databases do (MySQL for instance, does not). It is a PostgreSQL specific feature, and that tells you that this is not the common way to manage relationships in an RDBMS.
Using the two-table approach above, the SQL database can operate very efficiently. For instance, since users.id is a primary key, it is optimized for looking up records by id, using internal hashes.
As a rule of thumb, whenever you have a list or collection of things, you'll want to store them using one row per 'thing'.
Another down side of using arrays here is that the database cannot guarantee that the values in followers actually point to existing users. As far as the database is concerned, it is just a string. By specifying a foreign key the database will ensure data integrity, that is, you cannot store follower id's that do not exist.
You shouldn't worry about space. The text[] array approach might even use more space than using a second table. You can think of the text[] as a 'nested table' inside the users table. It would have to store the number and the length of the entries. In practice it won't make much of a difference.
The benefits of using a relationship table like followers far outweigh any concerns about space you might have. This is how RDBMS are meant to operate, and they are very efficient in how they do it.