Hot answers tagged


Public service announcement: never delete Really. Great way to get data corruption. You already had PostgreSQL installed, and you deleted the data dir without stopping the running server. So you now have some orphan PostgreSQL server processes that are managing data files that've been deleted, so they're no longer accessible in the file ...


It could be that you're using launchctl inside of Tmux or Screen. Tmux and Screen a terminal multiplexers that spawn multiple "screens" that you can easily switch between in a single terminal. For some reason unknown to me, running launchctl inside of Tmux never works, and emits the error Operation not permitted. Run it inside of a normal shell and it will ...


It appears that you have a database user named kuser, but there is no system user with that name. This is why you're able to get a postgres prompt as that user, but sudo fails. That user isn't able to create a database, because that account doesn't have the necessary permission. You can either grant that permission to the user, using the postgres account ...


Consider using Homebrew brew install postgresql It'll give you the necessary headers.


Is this your first install? Have you tried to run initdb /usr/local/var/postgres? That just solved the same issue, which has just happened to me after clearing an old system-wide PostgreSQL install and reinstalling it using Homebrew. Running brew info postgres is always useful as a reminder of the commands available after installing a package. postgresql ...


Another possibility is that you had a hard shutdown and the postgres process died without cleaning up its pid file. This happens to me when my laptop's battery dies. This solution is not for a production system, and you should really make sure the postgres daemon is not running, but I use my laptop for coding and I'm not worried about needing to regenerate ...


Ever Forward will answer your question: This is not an Internet URL, but it functions similarly. You now need to tell LibreOffice to connect to a specific database on a specific computer: dbname=mydb host=localhost Use the name of your database in the dbname part. I used localhost for the host part, since PostgreSQL is on the same computer, ...


Note that with PostgreSQL 9.0 (and probably newer) on Mac OS 10.6.8 (and probably older), in order to prevent the PostgreSQL server from auto-starting, you have to: Go to /Library/LaunchDaemons/ Open com.edb.launchd.postgresql-9.0.plist in an editor as root (replace 9.0 with your correct version number), e.g. sudo vim com.edb.launchd.postgresql-9.0.plist. ...


libpq, the underlying PostgreSQL client library, has the keepalives option to enable TCP keepalives. It looks like PgAdmin-III doesn't allow you to specify arbitrary connection parameters directly, but there's a workaround. When you look at the connection configuration in PgAdmin-III, you will see a "service" option. This refers to the connection service ...


This article and its comments might help: “FATAL: Ident authentication failed”, or how cool ideas get bad usage schemas


I know this Q is closed.. but here is more data information for someone who may stumble across this topic. Another form of datasource URL is in the format of: dbname=postgres hostaddr= port=5433 user=db_user password=libreoffice I needed the above, because the default port used by LibreBase is 5432, but I needed 5433. This URL format is ...


I was able to fix my problem by changing the postfix configuration to read: smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination instead of using smtpd_recipient_resrictions It turns out that after postfix 2.10.0, smtpd_relay_restrictions should be used instead of ...


Since I'm answering my own question, I was just going to delete it but others may find it useful in future. The solution is to brew uninstall postgresql then install it again. The reason it wasn't working was that the Macports install messed with some of the configs.


Once you've installed the PostgreSQL server with apt-get install postgresql-9.1, it's already set up and running so your steps #2 and #3 (run postgres and run initdb) are not necessary and in fact would conflict with what has already been set up. By running manually initdb you'll end up with two postgres clusters. The postgresql packages for Debian and ...


try this: wget --quiet -O - | sudo apt-key add - sudo sh -c 'echo "deb precise-pgdg main" >> /etc/apt/sources.list.d/postgresql.list' sudo apt-get update sudo apt-get install postgresql-9.3 pgadmin3 It worked fine for me. Source: How to: Install PostgreSQL ...


Install PostgreSQL, restore from backup, export the schema and data then import into MySQL.


pgAdmin -> Only for PostgreSQL SQL Workbench -> For many RDBMS


Try setting the database: psql -d postgres: echo `ALTER DATABASE x RENAME to y` | psql -d postgres "template1" or "postgres" should be available. See


Use psql: psql -f thefile.sql targetdatabase You may need to specify additional parameters, like username to connect as, host to connect to, etc.

5 Another response could be this: createdb: could not connect to database postgres: FATAL: user "joe" does not exist where your own login name is mentioned. This will happen if the administrator has not created a PostgreSQL user account for you. (PostgreSQL user accounts are distinct ...


You can set PuTTY to use UTF-8 from the configuration dialog when you connect. Go to Window -> Translation, and set "Received data assumed to be in which character set" to UTF-8. Also check that your locale is something ending in UTF-8 by running locale after connecting. If it's not, run locale -a to see all the locales you have available. If there are no ...


You could probably create a procedure to this, but out of the top of my head I'd just do a database dump (pg_dump) and search the file.


Your syntax is correct but only for PostgreSQL 9.0 and newer. In 8.3 you will have to list all tables by name: GRANT SELECT, INSERT, UPDATE, DELETE ON tab1, tab2, tab3 TO foo;


If machine gets turned off without going through the actual shutdown process, then PostgreSQL will refuse to start during the next boot up. This is because the PID file from before is still there and PostgreSQL thinks it is already running. That is what the error message in your edit is telling you. What you need to is remove the file from ...


I tried all of this to no avail after upgrading to Yosemite broke my postgres (installed via homebrew). Then I stumbled on this blog post: First I needed to create the missing directories that were apparently wiped out during the upgrade (thanks Apple!). $ cd ...


=> \a Output format is unaligned. => \f , Field separator is ",". => select 'John' "Name", 24 "Age"; Name,Age John,24


Try augeas. It offers both Python bindings and a command-line interface - augtool. [dba@pgsql ~]$ augtool augtool> defvar pghba /files/var/lib/pgsql/data/pg_hba.conf augtool> #################################### augtool> ls $pghba #comment[1] = this is a comment 1/ = (none) 2/ = (none) #comment[2] = this another comment 3/ = (none) augtool> ...


Look at: The location of stopwords for english dictionary is: $SHAREDIR/tsearch_data/english.stop for instance: /usr/share/postgresql/9.1/tsearch_data/english.stop

Only top voted, non community-wiki answers of a minimum length are eligible