and some of the functions in those files mention as
deprecated.
It would be greatly helpful if someone could guide me on this.
Thank you.
--
Regards,
Ashoke
the tags) and I am afraid I
would miss out on tags.
Thank you.
On Thu, Mar 13, 2014 at 5:47 AM, Kyotaro HORIGUCHI
horiguchi.kyot...@lab.ntt.co.jp wrote:
Hello,
On 03/12/2014 09:36 AM, Ashoke wrote:
Hi,
I am working on adding a functionality to PostgreSQL. I need to
parse
;
};
char *inp_str is added to the struct VacuumStmt in parsenodes.h
---
Only the newly added char *inp_str(that is different from ANALYZE) value is
NULL. I was able to retrieve the column name from va_cols.
Any help is appreciated. Thanks!
--
Regards,
Ashoke
copied from other _copy* functions.
On Fri, Jul 4, 2014 at 10:43 AM, Ashoke s.ash...@gmail.com wrote:
Hi,
--
I have defined a new command my_command in PostgreSQL. This command
takes the path of ANALYZE and inside analyze.c, I have a function to do
some operations
* as above, histogram_bounds for *TPCH
nation(n_name)* are : *ALGERIA,ARGENTINA,...*
This becomes an issue if the string has ',' (commas), like for example in
*n_comment* column of *nation* table.
Could someone point out the problem and suggest a solution?
Thank you.
--
Regards,
Ashoke
in
double quotes and some are not.
Ex : *c_address *column of* Customer *table
Why are there such inconsistencies? How is this determined?
Thank you.
On Tue, Jul 8, 2014 at 10:52 AM, Ashoke s.ash...@gmail.com wrote:
Hi,
I am trying to implement a functionality that is similar to ANALYZE
Ok, I was able to figure out that when strings contained 'spaces',
PostgreSQL appends them with double quotes.
On Tue, Jul 8, 2014 at 12:04 PM, Ashoke s.ash...@gmail.com wrote:
As a follow-up question,
I found some of the varchar column types, in which the histogram_bounds
are not being
