From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/8] perf scripts python: export-to-postgresql.py: Fix invalid input syntax for integer error
Date: Fri, 1 Mar 2019 14:54:26 -0300 [thread overview]
Message-ID: <20190301175426.GO13100@kernel.org> (raw)
In-Reply-To: <20190228130031.23064-4-adrian.hunter@intel.com>
Em Thu, Feb 28, 2019 at 03:00:26PM +0200, Adrian Hunter escreveu:
> Fix SQL query error "invalid input syntax for integer":
>
> Traceback (most recent call last):
> File "tools/perf/scripts/python/export-to-postgresql.py", line 465, in <module>
> do_query(query, 'CREATE VIEW calls_view AS '
> File "tools/perf/scripts/python/export-to-postgresql.py", line 274, in do_query
> raise Exception("Query failed: " + q.lastError().text())
> Exception: Query failed: ERROR: invalid input syntax for integer: ""
> LINE 1: ...ch_count,call_id,return_id,CASE WHEN flags=0 THEN '' WHEN fl...
> ^
> (22P02) QPSQL: Unable to create query
> Error running python script tools/perf/scripts/python/export-to-postgresql.py
Thanks, applied.
- Arnaldo
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
> Fixes: f08046cb3082 ("perf thread-stack: Represent jmps to the start of a different symbol")
> ---
> tools/perf/scripts/python/export-to-postgresql.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/scripts/python/export-to-postgresql.py b/tools/perf/scripts/python/export-to-postgresql.py
> index 30130213da7e..6358522a69f6 100644
> --- a/tools/perf/scripts/python/export-to-postgresql.py
> +++ b/tools/perf/scripts/python/export-to-postgresql.py
> @@ -478,7 +478,7 @@ if perf_db_export_calls:
> 'branch_count,'
> 'call_id,'
> 'return_id,'
> - 'CASE WHEN flags=0 THEN \'\' WHEN flags=1 THEN \'no call\' WHEN flags=2 THEN \'no return\' WHEN flags=3 THEN \'no call/return\' WHEN flags=6 THEN \'jump\' ELSE flags END AS flags,'
> + 'CASE WHEN flags=0 THEN \'\' WHEN flags=1 THEN \'no call\' WHEN flags=2 THEN \'no return\' WHEN flags=3 THEN \'no call/return\' WHEN flags=6 THEN \'jump\' ELSE CAST ( flags AS VARCHAR(6) ) END AS flags,'
> 'parent_call_path_id'
> ' FROM calls INNER JOIN call_paths ON call_paths.id = call_path_id')
>
> --
> 2.17.1
--
- Arnaldo
next prev parent reply other threads:[~2019-03-01 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190228130031.23064-1-adrian.hunter@intel.com>
[not found] ` <20190228130031.23064-2-adrian.hunter@intel.com>
2019-03-01 17:52 ` [PATCH 1/8] perf db-export: Add calls parent_id Arnaldo Carvalho de Melo
[not found] ` <20190228130031.23064-3-adrian.hunter@intel.com>
2019-03-01 17:52 ` [PATCH 2/8] perf scripts python: export-to-sqlite.py: Export " Arnaldo Carvalho de Melo
[not found] ` <20190228130031.23064-5-adrian.hunter@intel.com>
2019-03-01 17:54 ` [PATCH 4/8] perf scripts python: export-to-postgresql.py: " Arnaldo Carvalho de Melo
[not found] ` <20190228130031.23064-4-adrian.hunter@intel.com>
2019-03-01 17:54 ` Arnaldo Carvalho de Melo [this message]
[not found] ` <20190228130031.23064-6-adrian.hunter@intel.com>
2019-03-01 17:55 ` [PATCH 5/8] perf scripts python: exported-sql-viewer.py: Factor out TreeWindowBase Arnaldo Carvalho de Melo
[not found] ` <20190228130031.23064-7-adrian.hunter@intel.com>
2019-03-01 17:55 ` [PATCH 6/8] perf scripts python: exported-sql-viewer.py: Improve TreeModel abstraction Arnaldo Carvalho de Melo
[not found] ` <20190228130031.23064-8-adrian.hunter@intel.com>
2019-03-01 17:56 ` [PATCH 7/8] perf scripts python: exported-sql-viewer.py: Factor out CallGraphModelBase Arnaldo Carvalho de Melo
[not found] ` <20190228130031.23064-9-adrian.hunter@intel.com>
2019-03-01 18:20 ` [PATCH 8/8] perf scripts python: exported-sql-viewer.py: Add call tree Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190301175426.GO13100@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.