Hey there,

I'd rather not muck around with the hosts running the free tier. We don't
know a whole lot about what kinds of problems that might cause and any
issues would potentially impact a lot of users. We're quite strict about
not modifying Postgres for our own needs in general, but if you find a way
to get it done which you think we might be cool with, I'm happy to discuss
rolling that out. I've also forwarded your question on to some Postgres
hackers I know to see if they have any bright ideas.

-p


On Sat, Mar 2, 2013 at 3:28 PM, Nickolay Kolev <[email protected]> wrote:

> Hi Peter,
>
> thank you for your offer! I am not on a production plan (yet). Still using
> the free tier.
>
> I guess it boils down to getting the data to the DB and having "CREATE
> TEXT SEARCH DICTIONARY ..." and "CREATE TEXT SEARCH CONFIGURATION ..."
> take that data from somewhere else than files in $SHAREDIR.
>
> The first part is not that hard (one can access the DB with psql after all
> and dump the data in a table) but the second one depends on Postgres
> support. So far  have found nothing in the docs that suggests that Postgres
> can read dictionary data from anywhere else than $SHAREDIR, let alone use
> data in a table.
>
> Best,
> Nickolay
>
> On Sunday, March 3, 2013 12:16:31 AM UTC+1, Peter van Hardenberg wrote:
>
>> Hi Nickolay,
>>
>> we haven't figured this out yet. Assuming you're on a production plan,
>> you could email me the requisite dictionary and I can try dropping it in
>> place for you on an experimental basis. Coming up with a better mechanism
>> for this is an interesting project. Ideally, it should be something you can
>> do yourself through some built-in mechanism in Postgres.
>>
>>
>> On Sat, Mar 2, 2013 at 2:56 PM, Nickolay Kolev <[email protected]> wrote:
>>
>>> Hi all,
>>>
>>> is there a way of adding a text search dictionary and configuration to a
>>> Heroku Postgres DB? One cannot access $SHAREDIR in order to put the
>>> dictionary files there, so an alternative is required.
>>>
>>> I would not mind putting the dictionary files in migrations if required.
>>>
>>> I am very happy with the performance and results of the TSearch2 German
>>> Compound dictionary and would like to use it in a Heroku-hosted project.
>>>
>>> Best,
>>> Nickolay
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Heroku" group.
>>>
>>> To unsubscribe from this group, send email to
>>> heroku+un...@**googlegroups.com
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/**group/heroku?hl=en_US?hl=en<http://groups.google.com/group/heroku?hl=en_US?hl=en>
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Heroku Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to heroku+un...@**googlegroups.com.
>>>
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>> .
>>>
>>>
>>>
>>
>>  --
> --
> You received this message because you are subscribed to the Google
> Groups "Heroku" group.
>
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en_US?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Heroku Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Heroku" group.

To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to