madssj.com - Latest Comments

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

Eduard von Feek — Thu, 23 Jun 2016 12:25:03 -0000

I got the same error message with one of my databases. Its name included a dash, e.g. `my-database`.

Iff a database name includes dash characters, `pg_dumpall` will generate a `\connect` statement with its database name parameter in double quotes, e.g. the full dump will won't include the statement `\connect my-database`, but `\connect "my-database"`.

The solution / workaround then is to run `pg_extract_db` with the database name in (shell-escaped) double quotes:

pgx_extract_db big-dump-file.sql \"my-database\" >my-database.sql

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

rune_kg — Thu, 26 Dec 2013 19:19:29 -0000

Thx for the linkback!! Cheers

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

madssj — Mon, 16 Dec 2013 05:22:14 -0000

It worked wonderfully in 2010, the dump format might have changed. I'll add a link in the top for your updated gist - thanks!

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

rune_kg — Fri, 13 Dec 2013 05:26:10 -0000

Thank you so much for this! On my system it did not work for the last database in the file, because "end_point" would be empty. I also needed to remove OWNER,REVOKE and GRANT commands to make the restore work with other database credentials. I did just that, added an install command, a list dbs command and put it in a gist here: https://gist.github.com/run...

You saved me much hassle, and the cool thing about your solution compared to the other floating around the interwebs is that its actually fast enough for large files too! Great work!

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

madssj — Tue, 04 Jun 2013 04:23:42 -0000

Then it can't find a line that says "\connect dbname" in your dump file.

Feel free to tinker with the script.

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

Brent O'Connor — Mon, 03 Jun 2013 12:20:19 -0000

I'm not sure why, but I'm getting, "error: start or end not found" when I run this script.

Re: Django – sharing a memcached instance

Mads Sülau Jørgensen — Wed, 23 Mar 2011 12:08:55 -0000

Agreed. I've updated the post to reflect the fact, that django 1.3 was released last night.

Re: Django – sharing a memcached instance

Andrew Ash — Tue, 22 Mar 2011 20:20:02 -0000

The patch that Curious User linked to has been approved in Django 1.3, which should be out shortly.

http://code.djangoproject.c...

http://docs.djangoproject.c...

Re: Asynchronous socket server in python

Mads Sülau Jørgensen — Mon, 01 Nov 2010 08:32:20 -0000

True. conn should be sock.

Re: Asynchronous socket server in python

wildman — Sun, 31 Oct 2010 18:21:17 -0000

error in line 22:
asynchat.async_chat.init(self, sock=conn)

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

Mads Sülau Jørgensen — Thu, 14 Oct 2010 17:33:38 -0000

You're very welcome.

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

Kai — Thu, 14 Oct 2010 08:04:33 -0000

You just saved me a lot of work. Thanks!

Re: Django – sharing a memcached instance

Mads Sülau Jørgensen — Thu, 01 Jul 2010 10:33:27 -0000

Oh, that's even better!

I'll stick it in the post, thanks again :)

Re: Django – sharing a memcached instance

Curious User — Thu, 01 Jul 2010 10:31:30 -0000

Thanks for your quick reply!

Note a patch has been submitted: http://code.djangoproject.c...

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

Mads Sülau Jørgensen — Thu, 01 Jul 2010 10:29:13 -0000

Right, replaced with echo "foo" >&2.

Thanks.

Re: Django – sharing a memcached instance

Mads Sülau Jørgensen — Thu, 01 Jul 2010 10:26:36 -0000

If you set CACHE_MIDDLEWARE_KEY_PREFIX and use the memcached_key_prefix cache backend, both will add a key to the cache key.

So, if the CacheMiddleware were to insert a key called frontpage, it would then prefix it with the above setting, and pass it along to the cache backend, which then again prefixes the key. You then end up with a key called CACHE_MIDDLEWARE_KEY_PREFIX + cache_backend_prefix + cache_key which is suboptimal.

Re: Django – sharing a memcached instance

Curious User — Thu, 01 Jul 2010 10:00:15 -0000

Please explain "kind of conflict".

I appreciate you taking the time to post this, as have countless other non-commenters.

Re: Extracting a single database from a pg_dumpall PostgreSQL dump

J. Christopher Pereira — Fri, 25 Jun 2010 23:57:01 -0000

Redirection to stderr with "> 2" is not working.

Re: Mercurial trac commit hook

Pascal — Thu, 26 Nov 2009 18:01:25 -0000

Thanks for this plugin.

I have try this plugin without success with Trac0.12-multirepos
I have this error :
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/trachook.py", line 210, in hook
trac_hook.update(c, r, url)
File "/usr/lib/python2.4/site-packages/trachook.py", line 88, in update
self.env.href = Href(url)
TypeError: 'str' object is not callable
error: changegroup hook raised an exception: 'str' object is not callable

???

Re: Actionscript 3 – posting XML data with URLLoader

Niklas — Fri, 13 Nov 2009 10:03:32 -0000

Jeg kunne godt tænke mig et php script hvor jeg kunne rette i min xml :P

Re: Mercurial trac commit hook

math — Fri, 30 Oct 2009 14:35:07 -0000

Hmm, just copying the trachook.py to the place gave me an permission error, that normal users which checkin doesn't have the permission to change /srv/trac/myProject files. How did you solved this??

Re: Building postgresql8x and psycopg2 for x86_64 and i386 on Snow Leopard (OS X 10.6)

Adam Nelson — Tue, 13 Oct 2009 22:17:05 -0000

Make sure you have (at least for me) 10.4 development tools turned on when installing Xcode. Otherwise I got errors like:

ld: library not found for -lbundle1.o
collect2: ld returned 1 exit status
error: command 'gcc-4.0' failed with exit status 1

Re: Django compatible PyAMF test client

Sam Ahn — Fri, 11 Sep 2009 14:02:16 -0000

This is great. I'm surprised it wasn't already there.

Re: Building postgresql8x and psycopg2 for x86_64 and i386 on Snow Leopard (OS X 10.6)

Mads Sülau Jørgensen — Fri, 04 Sep 2009 08:18:37 -0000

@Rune, Hm, I was either using bash or zsh at the time (probably bash). I'll correct it by removing the checks, chances are they're not needed anyway.

Thanks.

Re: Building postgresql8x and psycopg2 for x86_64 and i386 on Snow Leopard (OS X 10.6)

Rune Bromer — Fri, 04 Sep 2009 06:59:30 -0000

What shell are you using? I get a syntax like error when I try to run: [ -f "ld.sh" -a -n -f "files/ld.sh" ] && sudo mv ld.sh files/

It fails with the error message [: too many arguments.

Also, unless I have the hole permission things wrong you need a sudo in front of the "mkdir files".