WhiteRider wrote:Ah, yes - there have been issues related to aliases before - did you set the alias before you imported?
Not sure about it, since I've been switching that alias back and forth. I'll just forget about this for now and let you know if it happens again in the future without me creating/removing aliases all the time.
WhiteRider wrote:Into the same networked database?
The recommendation is not to do this as postgres (or at least the way PT3 uses it) is not thread-safe. A few people have reported that they have done this without problems, but we can't guarentee the safety of the database.
Yeah, the same network database. I haven't been importing at the same time and if this is the case, I won't do it in the future.