Did you initialize the DB cluster (initdb -D /path/to/data)?
Did you configure the installation (postgres.conf file)?
Does homebrew.mxcl.postgresql where the data lives?
when you run "ps -ef|grep -i postg", do you see the postmaster and other
postgres executables running?
> On Mar 13, 2016, at 0
\
--with-tclconfig=/usr/local/Cellar/tcl-tk/8.6.4/lib/ \
--with-perl \
--with-python
> On Mar 11, 2016, at 22:40, Tom Lane wrote:
>
> Chris Ruprecht writes:
>> today, I built PG 9.5.1 on my Mac. Everything went fine with the build, as
>> usual but after installing
Hey Tom,
I can't reboot right now, working on a client's machine remotely, but I'l test
that tomorrow and keep you posted. Thanks for the link.
> On Mar 11, 2016, at 22:40, Tom Lane wrote:
>
> I'd bet a nickel this is caused by El Capitan's "System Integrity
> Protection" deciding that your ps
001be6c in refresh_utf8format ()
Any idea how to fix this?
Thanks,
Chris.
best regards,
chris
--
chris ruprecht
database grunt and bit pusher extraordinaíre
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Thanks guys. I know what I will spend the night, doing ;).
> On Oct 27, 2014, at 16:33 , Tom Lane wrote:
>
> Chris Ruprecht writes:
>> I can export the data out of that database into flat files just fine, but
>> then I try to import the data to Postgres, I'
I'm using
psql mydb
# copy attachments FROM '/opt/tmp/clientdata/sql-data-p/attachments.dat' with
NULL as 'NULL';
to load the database back in. The psql command runs on the same box as the DB
server.
If I had my way, I'd store the binary somewhere and keep a reference to it in
the database
d LATIN1, SQL_ASCII, UTF-8, nothing works. I even tried to make the data
type 'bytea', no luck. I'd love to have a "NO-CONVERSION" option on the copy
command that just takes what ever bytes come along and doesn't try to interpret
them.
Any ideas of what I can do to
