# Postgresql database connected but history tag is not plotting in easy chart **URL:** \ **Category:** Ignition\ **Created:** [May 30, 2017, 11:04am UTC](https://forum.inductiveautomation.com/t/postgresql-database-connected-but-history-tag-is-not-plotting-in-easy-chart/14415 "2017-05-30T11:04:01Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![BHASKAR](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@BHASKAR](https://forum.inductiveautomation.com/u/BHASKAR)\ **Post date:** [May 30, 2017, 11:04am UTC](https://forum.inductiveautomation.com/t/postgresql-database-connected-but-history-tag-is-not-plotting-in-easy-chart/14415/1 "2017-05-30T11:04:01Z")
I am using Ignition 7.9 and postgresql database. Database status is valid and connected through default user postgres. But when I want to display the history tag in easy chart, the data is plotting. Same tag if I connected it through MySQL, it is working.What may be the reason. There are no any error messages. Is it we need to create table also in postgresql server? I have created only database and connected. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 30, 2017, 12:18pm UTC](https://forum.inductiveautomation.com/t/postgresql-database-connected-but-history-tag-is-not-plotting-in-easy-chart/14415/3 "2017-05-30T12:18:17Z")
Ignition will automatically create the necessary tables when you’ve configured history correctly. Double-check that you have the connection set up as a history provider and that you’ve selected this history provider in the tags you wish to plot. ---
**Author:** ![BHASKAR](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@BHASKAR](https://forum.inductiveautomation.com/u/BHASKAR)\ **Post date:** [June 1, 2017, 9:28am UTC](https://forum.inductiveautomation.com/t/postgresql-database-connected-but-history-tag-is-not-plotting-in-easy-chart/14415/4 "2017-06-01T09:28:32Z")
It got corrected; it was date mismatch with the database server & client… any way thanks for your reply…