On Sat, Aug 26, 2017 at 10:10 AM, yang...@highgo.com
wrote:
> Hi all,
>
> Now we have had the range / list partition, but hash partitioning is not
> implemented yet.
> Attached is a POC patch based on the v10Beta2 to add the
> hash partitioning feature.
> Although we will
ows)
Can not detach / attach / drop partition table.
Best regards,
young
yonj1e.github.io
yang...@highgo.com
Hi all,
Now we have had the range / list partition, but hash partitioning is not
implemented yet.
Attached is a POC patch based on the v10Beta2 to add the hash partitioning
feature.
Although we will need more discussions about the syntax and other
specifications before going ahead the project
You are right. When I add those codeļ¼ it really give me a strong bad smell.
It not worth these effort.
Thanks for your reply and suggestion.
--
Sincerely
Fan Yang
; *line != NULL; line++)
PG_CMD_PUTS(*line);
}
@@ -1889,6 +1922,7 @@ setup_schema(FILE *cmdfd)
{
char **line;
char **lines;
+char *escaped;
lines = readfile(info_schema_file);
@@ -1905,11 +1939,13 @@ setup_schema(FILE *cmdfd)
" WHERE implementation_info_name = 'DBMS
VERSION';\n\n",
infoversion);
+escaped = escape_quotes(features_file);
PG_CMD_PRINTF1("COPY information_schema.sql_features "
" (feature_id, feature_name, sub_feature_id, "
" sub_feature_name, is_supported, comments) "
" FROM E'%s';\n\n",
- escape_quotes(features_file));
+ escaped);
+free(escaped);
}
/*
Hope this patch can fix this problem.
--
Yang Fan
ement.
The problem is reproducable with the following query.
SELECT array_position(ids, (1, 1))
FROM (VALUES (ARRAY[(0, 0)]), (ARRAY[(1, 1)])) AS _(ids);
From 8868ae0050ec382bc1bae2b993742eb2a40bbb14 Mon Sep 17 00:00:00 2001
From: Junseok Yang
Date: Thu, 8 Dec 2016 18:25:21 -0800
Subject: [PATCH
I run "pg_upgrade -xx" fromPostgreSQL8.3 to PostgreSQL9.4.5 on window server
2008. It will show some wrong information:
cannot write to log file pg_upgrade_internal.log
Failure, exiting.
It seems that the upgrade can be successful on window 7. It seems to be a
permissions problem. I get some i
e won't be considered for 9.5 but I'd like to implement it and
hopefully get it incorporated into 9.6.
Thanks,
Zhaomo
On Wed, Sep 23, 2015 at 11:54 AM, Stephen Frost wrote:
> * Zhaomo Yang (zmp...@gmail.com) wrote:
>> > Just a side-note, but your mail client doesn't seem to
Stephen,
> Just a side-note, but your mail client doesn't seem to get the quoting
> quite right sometimes, which can be confusing. Not sure if there's
> anything you can do about it but wanted to let you know in case there
> is.
Sorry about this. From now on I'll use the plain text mode for msgs
Stephen,
It'd be great if others who are interested can help define the grammar
> changes necessary
> and perhaps even help with the code aspect of it.
I'd like to help on both. Can you elaborate a little bit more, especially
on the code aspect?
I don't buy that argument.
It is agreed that blin
Stephen,
> I agree that if we force a single visibility policy for all commands
> then we wouldn't need the USING clauses for UPDATE and DELETE, but we
> would certainly need *some* policy for DELETE to prevent users from
> being able to delete records that they aren't supposed to be allowed to.
>
some related
discussions (applying SELECT policy to other commands).
Thanks,
Zhaomo
On Tue, Aug 25, 2015 at 8:17 AM, Stephen Frost wrote:
> Zhaomo,
>
> * Zhaomo Yang (zmp...@gmail.com) wrote:
> > > If no NEW or OLD is used, what happens? Or would you have
> > > to alw
Stephen,
If no NEW or OLD is used, what happens? Or would you have
> to always specify OLD/NEW for UPDATE, and then what about for the other
> policies, and the FOR ALL policies?
I should be clearer with references to OLD/NEW. SELECT Predicates cannot
reference any of them.
INSERT predicates ca
In case you missed the link to the previous discussion at the bottom,
http://www.postgresql.org/message-id/CAHGQGwEqWD=ynqe+zojbpoxywt3xlk52-v_q9s+xofckjd5...@mail.gmail.com
Hi,
This thread has a pretty thorough discussion of pros and cons of applying
SELECT policy to other commands. Besides what have been mentioned, I think
there is another potential pro: we can enable references to pseudorelations
OLD and NEW in predicates. Now, for UPDATE, the references to the tar
Hello,
I've performed some tests on pg_strom according to the wiki. But it seems that
queries run slower on GPU than CPU. Can someone shed a light on what's wrong
with my settings. My setup was Quadro K620 + CUDA 7.0 (For Ubuntu 14.10) +
Ubuntu 15.04. And the results was
with pg_strom
==
>
> Just to be clear, the idea of a global temp table is that the table def
> is available to all users, but the data is private to each session?
The table def is visible to all sessions and persistent, but the data is
private to each session and temporary.
Thanks,
Zhaomo
> Sounds fine in general. I'm a bit curious to know what are the locking
implications of > vivifying the table on access.
The locking implications depend on how we interpret the existing commands
in the context of global temp tables and I think we should discuss and
agree on the behaviors of the c
> there is other question - what is effect of ALTER TABLE of global temp
table on
> instances of this table in active sessions?
As I said, we need to first agree on the behaviors of the existing
commands. I can think of two options now for ALTER TABLE: 1) only allow
ALTER TABLE when there is no
session.
Thanks,
Zhaomo
On Tue, Jul 7, 2015 at 11:53 PM, Pavel Stehule
wrote:
> Hi
>
>
> 2015-07-08 9:08 GMT+02:00 Zhaomo Yang :
>
>> > more global temp tables are little bit comfortable for developers,
>> I'd like to emphasize this point. This feature does much mor
> more global temp tables are little bit comfortable for developers,
I'd like to emphasize this point. This feature does much more than saving a
developer from issuing a CREATE TEMP TABLE statement in every session. Here
are two common use cases and I'm sure there are more.
(1)
Imagine in a web a
(e.g.
this mail list) so that people can try it.
Thanks,
Zhaomo
On Sat, Sep 13, 2014 at 4:00 PM, Stephen Frost wrote:
> Zhaomo,
>
> * Zhaomo Yang (zhy...@cs.ucsd.edu) wrote:
>> > Have you considered just using a regular, but unlogged, table? That
>> > wou
CAC cards with client-side certificates.
You are absolutely right. I should've explained it better. I just
wanted to show how authentication works and skipped all the hashing
part.
Thanks,
Zhaomo
On Fri, Sep 5, 2014 at 5:52 PM, Stephen Frost wrote:
> Zhaomo,
>
> As an FYI- we gene
hen Frost wrote:
> Zhaomo,
>
> * Zhaomo Yang (zhy...@cs.ucsd.edu) wrote:
>> I am a graduate student from UC San Diego. My adviser, Dr. Kirill
>> Levchenko, and I have been working on a web/DB security project for
>> the last few months. Since fine-grained access control in
would like to take part in implementing it. Please feel free to
contact us if you have any questions.
Zhaomo Yang zhy...@ucsd.edu
Kirill Levchenko klevc...@ucsd.edu
References:
[1] S. Chaudhuri, T. Dutta, and S. Sudarashan. Fine Grained
Authorization Through Predicated Grants. In
Hi folks,
I'm working on a project where I need to run some commands/functions when
SELECT are executed on certain tables. I looked at the rule system and
found the following paragraph in the documentation:
"Currently, there can be only one action in an ON SELECT rule, and it
must be an uncondi
Hi Hackers!
This is Zheng Yang from National University of Singapore.
I'm very glad to know that my proposal, "Enhancing Foreign-data Wrapper (FDW)
functionality for PostgreSQL", has been accepted
by this year's Google Summer of Code!
Thank you guys for the v
o int[][].
- Original Message
From: Robert Haas
To: Sophie Yang
Cc: Pavel Stehule ; pgsql-hackers@postgresql.org
Sent: Thursday, March 5, 2009 6:51:48 PM
Subject: Re: [HACKERS] Use array in a dynamic statement
On Thu, Mar 5, 2009 at 8:32 PM, Sophie Yang wrote:
>
> I was wonderin
by the
length of the dewy index, which is equivalent to sort the nodes by their tree
depth. That's what I try to achieve. Maybe someone has different idea to
implement the function?
Thanks,
Sophie
- Original Message
From: Pavel Stehule
To: Sophie Yang
Cc: pgsql-ha
Hi,
I am trying to implement a PL/PgSQL function as following:
CREATE OR REPLACE FUNCTION sort_by_d_idx (nids INT[][], tbl_name VARCHAR)
RETURNS varchar[]
AS $$
DECLARE
result varchar[];
BEGIN
EXECUTE 'SELECT ARRAY(SELECT t.idx FROM generate_series(array_lower($1,1),
array_upper($1,1)) AS s
GIST structure is also available
in Postgresql.
Thanks again.
Zhen Yang
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Zhen Yang <[EMAIL PROTECTED]> writes:
> > What are the C interface functions in Postgresql to add indexes?
>
> You will need to study the source code f
indexes into
the Postgresql DB. What are the C interface functions in Postgresql
to add indexes? Do I need to handle things like memory buffer
management, disk storage management when implementing the indexes?
Thanks in advance.
Sincerely,
Zhen Yang
__
Do you Yahoo
32 matches
Mail list logo
