Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> ...
> Or we could continue to use symlinks, and just create them ourselves in
> the backend.
But you'd still need some built-in understanding about where the table
is Really Supposed To Be, because you'd need to be able to create and
delete the symlinks on the fly when the table grows past a 1-Gb segment
boundary (or is shrunk back again by vacuum!).
AFAICS, a reasonable solution still requires storing a location path
for each table --- so you might as well just use that path directly.
regards, tom lane