From a bit of googling, it looks like this might be Drupal's fault in that it doesn't keep going when a statement within a transaction fails. Nevertheless, this probably shouldn't crash. It prevents the creation of any new users. Here's the error message I get from Drush (same thing from the web):

PDOException: SQLSTATE[25P02]: In failed sql transaction: 7 ERROR: current transaction is aborted, [error]
commands ignored until end of transaction block: SELECT column_name, data_type, column_default FROM
information_schema.columns WHERE table_schema = :schema AND table_name = :table AND (data_type = 'bytea' OR
(numeric_precision IS NOT NULL AND column_default LIKE :default)); Array
(
[:schema] => public
[:table] => url_alias
[:default] => %nextval%
)
in drupal_write_record() (line 7166 of /var/www/example.com/www/public/includes/common.inc).

CommentFileSizeAuthor
#3 2083065-postgres-string-int-transaction-killing-error.patch440 bytesJohn Franklin
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

John Franklin’s picture

John Franklin CreditAttribution: John Franklin commented
Issue summary: View changes

I get the same thing using BlogAPI to post new blog entries.

John Franklin’s picture

John Franklin CreditAttribution: John Franklin commented

The actual error is a previous SQL statement that fails. My postgres log includes the following error:

2014-04-10 12:15:50 EDT ERROR:  invalid input syntax for integer: "franklin" at character 422
2014-04-10 12:15:50 EDT STATEMENT:  SELECT base.uid AS uid, base.name AS name, base.pass AS pass, base.mail AS mail, base.theme AS theme, base.signature AS signature, base.signature_format AS signature_format, base.created AS created, base.access AS access, base.login AS login, base.status AS status, base.timezone AS timezone, base.language AS language, base.picture AS picture, base.init AS init, base.data AS data
	FROM 
	users base
	WHERE  (base.uid IN  ('franklin'))
John Franklin’s picture

John Franklin CreditAttribution: John Franklin commented
FileSize
2083065-postgres-string-int-transaction-killing-error.patch440 bytes

Here's a fix that works for my blogapi issue. @mjorlitzky, if this also fixes your issue, then we should file this as a core bug. Apply this patch to core.

orlitzky’s picture

orlitzky CreditAttribution: orlitzky commented

I still get the same error I'm afraid.

John Franklin’s picture

John Franklin CreditAttribution: John Franklin commented

Do you have any errors in your postgres logs?

orlitzky’s picture

orlitzky CreditAttribution: orlitzky commented

Yep, same error it looks like (I tried before patching, too).

Apr 12 11:14:28 [postgres] [4-1] ERROR:  invalid input syntax for integer: "testuser" at character 422
Apr 12 11:14:28 [postgres] [4-2] STATEMENT:  SELECT base.uid AS uid, base.name AS name, base.pass AS pass, base.mail AS mail, base.theme AS theme, base.signature AS signature, base.signature_format AS signature_format, base.created AS created, base.access AS access, base.login AS login, base.status AS status, base.timezone AS timezone, base.language AS language, base.picture AS picture, base.init AS init, base.data AS data
Apr 12 11:14:28 [postgres] [4-3] _FROM 
Apr 12 11:14:28 [postgres] [4-4] _users base
Apr 12 11:14:28 [postgres] [4-5] _WHERE  (base.uid IN  ('testuser')) 
Apr 12 11:14:28 [postgres] [5-1] ERROR:  current transaction is aborted, commands ignored until end of transaction block
Apr 12 11:14:28 [postgres] [5-2] STATEMENT:  SELECT column_name, data_type, column_default FROM information_schema.columns WHERE table_schema = 'public' AND table_name = 'url_alias' AND (data_type = 'bytea' OR (numeric_precision IS NOT NULL AND column_default::text LIKE '%nextval%'))