On Sun, Nov 4, 2012 at 3:39 AM, Craig Ringer <ring...@ringerc.id.au> wrote:
> On 11/04/2012 08:47 AM, Matthew Gerber wrote:
>
>
> Here is the command that was executing when the 0xC0000409 exception was
> raised:
>
> INSERT INTO places (bounding_box,country,full_name,id,name,type,url)
>
> VALUES
>
> (st_transform_null(ST_GeometryFromText('POLYGON((-97.034085
> 32.771786,-97.034085 32.953966,-96.888789 32.953966,-96.888789
> 32.771786,-97.034085 32.771786))',4326),26918),'United States','Irving,
> TX','dce44ec49eb788f5','Irving','city','
> http://api.twitter.com/1/geo/id/dce44ec49eb788f5.json'),
>
>
> OK, so you're using PostGIS. What other extensions are loaded? PL/R? Any
> other PLs?
>
PostGIS is the only extension that I added to the default configuration. I
didn't change anything else.
>
> Can you show the definition of the table `places`, incuding any associated
> triggers, etc? Use `\d+` in psql for the table def'n.
>
Here the definition of the places table:
twitter=# \d+ places
Table "public.places"
Column | Type | Modifiers | Storage | Stats
target |Description
--------------+-------------------------+-----------+----------+--------------+-------------
bounding_box | geometry(Polygon,26918) | | main
| |
country | character varying | | extended
| |
full_name | character varying | | extended
| |
id | character varying | not null | extended
| |
name | character varying | | extended
| |
type | character varying | | extended
| |
url | character varying | | extended
| |
Indexes:
"places_pkey" PRIMARY KEY, btree (id)
"places_bounding_box_idx" gist (bounding_box)
"places_type_idx" btree (type)
Referenced by:
TABLE "tweets" CONSTRAINT "tweets_place_id_fkey" FOREIGN KEY (place_id)
REFERENCES places(id) ON DELETE CASCADE
Has OIDs: no
>
> Please also post the query plan. http://explain.depesz.com/ is useful for
> this.
>
Here is the query plan:
QUERY PLAN
Insert on public.places (cost=0.00..0.01 rows=1 width=0) (actual
time=1.000..1.000 rows=0 loops=1)
-> Result (cost=0.00..0.01 rows=1 width=0) (actual time=0.001..0.001
rows=1 loops=1)
Output:
'01030000202669000001000000050000005E8705A4E32C38C1EE553AE6E95E
4D41086A91990B1B38C11620AF9784874D41FCA5741676E437C19436654287814D41C43E11332BF6
37C17C863746F0584D415E8705A4E32C38C1EE553AE6E95E4D41'::geometry(Polygon,26918),
'United States'::character varying, 'Irving, TX'::character varying,
'dce44ec49e
b788f5'::character varying, 'Irving'::character varying, 'city'::character
varyi
ng, 'http://api.twitter.com/1/geo/id/dce44ec49eb788f5.json'::charactervarying
Total runtime: 1.157 ms
(4 rows)
>
>
> So I attached the VS debugger, but the server died without raising an
> exception in VS. Not sure what's going on here.
>
>>
>> Try creating a directory called "crashdumps" in the data directory, at
> the same level as "pg_xlog" and "pg_clog" etc. Give the "postgresql" user
> the "full control" permission on it. Then run the test again.
>
Running it now.
>
> Do any minidump files appear in the directory? If so, you can examine them
> with windbg or Visual Studio to see where the crash happened.
>
Will try it.
Thanks for your help so far, guys. Hopefully we get somewhere on this...
Matt
