On 03.07.2012 15:13, Robert Haas wrote:
On the substance of the patch, I believe the reason why this is
currently disallowed is because the TLI is implicitly taken from the
running system, and on the standby that might be the wrong value.
Yeah, I believe that's the reason. So the question is,
I think Tom's point is, there are tons of applications which define
their own int64_t (at least in 2005).
Also pg_config.h has:
#define HAVE_STDINT_H 1
and this suggests that PostgreSQL adopts to platforms which does not
have stdint.h. If so, we need to take care of such platforms
Currently lo_initialize() throws an error if one of oids are not
available. I doubt we do the same way for 64-bit functions since this
will make 9.3 libpq unable to access large objects stored in pre-9.2
PostgreSQL servers.
It seems to me the situation to split the case of pre-9.2 and
于 2012/9/19 7:22, Bruce Momjian 写道:
On Mon, Sep 17, 2012 at 05:07:23PM -0400, Bruce Momjian wrote:
# select * from pg_tables where tablename='sql_features';
schemaname | tablename | tableowner | tablespace |
hasindexes | hasrules | hastriggers
I think Tom's point is, there are tons of applications which define
their own int64_t (at least in 2005).
Also pg_config.h has:
#define HAVE_STDINT_H 1
and this suggests that PostgreSQL adopts to platforms which does not
have stdint.h. If so, we need to take care of such platforms
2012/9/21 Tatsuo Ishii is...@postgresql.org:
I think Tom's point is, there are tons of applications which define
their own int64_t (at least in 2005).
Also pg_config.h has:
#define HAVE_STDINT_H 1
and this suggests that PostgreSQL adopts to platforms which does not
have stdint.h. If so,
On Friday, September 21, 2012 1:23 AM Pavel Stehule wrote:
Basic stuff:
- Patch applies OK. but offset difference in line numbers.
- Compiles with errors in contrib [pg_stat_statements, sepgsql] modules
- Regression failed; one test-case in COPY due to incomplete test-case
Hmm, I see. Please deliver the 64bit integer argument as reference,
and don't forget endian translations here.
I thought pgPutInt64() takes care of endianness. No?
It works inside of the PGfn(), when isint = 1 towards pointer data type.
In my sense, it is a bit problem specific solution.
2012/9/21 Tatsuo Ishii is...@postgresql.org:
Hmm, I see. Please deliver the 64bit integer argument as reference,
and don't forget endian translations here.
I thought pgPutInt64() takes care of endianness. No?
It works inside of the PGfn(), when isint = 1 towards pointer data type.
In my
I thought pgPutInt64() takes care of endianness. No?
It works inside of the PGfn(), when isint = 1 towards pointer data type.
In my sense, it is a bit problem specific solution.
So, I'd like to see other person's opinion here.
I think we cannot change this because we want to keep the
2012/9/21 Tatsuo Ishii is...@postgresql.org:
I thought pgPutInt64() takes care of endianness. No?
It works inside of the PGfn(), when isint = 1 towards pointer data type.
In my sense, it is a bit problem specific solution.
So, I'd like to see other person's opinion here.
I think we cannot
2012/9/21 Tatsuo Ishii is...@postgresql.org:
I thought pgPutInt64() takes care of endianness. No?
It works inside of the PGfn(), when isint = 1 towards pointer data type.
In my sense, it is a bit problem specific solution.
So, I'd like to see other person's opinion here.
I think we cannot
On Tuesday, September 18, 2012 6:02 PM Fujii Masao wrote:
On Mon, Sep 17, 2012 at 4:03 PM, Amit Kapila amit.kap...@huawei.com wrote:
Approach-2 :
Provide a variable wal_send_status_interval, such that if this is 0, then
the current behavior would prevail and if its non-zero then KeepAlive
On Fri, Sep 21, 2012 at 5:17 AM, Josh Kupershmidt schmi...@gmail.com wrote:
If the argument for moving pg_reorg into core is faster and easier
development, well I don't really buy that.
I don't see any problem in having pg_reorg in PGXN instead.
I've tried adding a META.json to the project
Excerpts from Amit Kapila's message of vie sep 21 02:26:49 -0300 2012:
On Thursday, September 20, 2012 7:13 PM Alvaro Herrera wrote:
Well, there is a difficulty here which is that the number of processes
connected to databases must be configured during postmaster start
(because it
On 9/20/12 11:55 PM, Andres Freund wrote:
On Monday, September 17, 2012 03:58:37 PM Tom Lane wrote:
OK, that explains why we've not seen a blizzard of trouble reports.
Still seems like a good idea to fix it ASAP, though.
Btw, I think RhodiumToad/Andrew Gierth and I some time ago helped a user
On Fri, Sep 21, 2012 at 9:33 PM, Daniele Varrazzo
daniele.varra...@gmail.com wrote:
On Fri, Sep 21, 2012 at 5:17 AM, Josh Kupershmidt schmi...@gmail.com
wrote:
If the argument for moving pg_reorg into core is faster and easier
development, well I don't really buy that.
I don't see any
On Fri, Sep 21, 2012 at 1:00 PM, Hitoshi Harada umi.tan...@gmail.comwrote:
I'm not familiar with pg_reorg, but I wonder why we need a separate
program for this task. I know pg_reorg is ok as an external program
per se, but if we could optimize CLUSTER (or VACUUM which I'm a little
Kohei KaiGai kai...@kaigai.gr.jp writes:
My preference is nothing are changed both pg_getmsgint64() of the backend
and routines under PQfn() of the libpq. Isn't it unavailable to deliver int64-
value after the endian translation on the caller side?
Right. If we had to change anything on the
On Friday, September 21, 2012 03:30:31 PM Marko Tiikkaja wrote:
On 9/20/12 11:55 PM, Andres Freund wrote:
On Monday, September 17, 2012 03:58:37 PM Tom Lane wrote:
OK, that explains why we've not seen a blizzard of trouble reports.
Still seems like a good idea to fix it ASAP, though.
During the execution of ProcessUtility() function in
/src/backend/xxx/utility.c,
the CreateStmt node type is processed to create a table.
Is there a global function in the context of the backend process that
will deliver what the current database and schema names?
The querystring cannot be
On 02.07.2012 15:08, Amit Kapila wrote:
Attached is a Patch to change the parsing of pg_ident.conf to make it
similar to pg_hba.conf.
This is based on Todo Item:
http://archives.postgresql.org/pgsql-hackers/2011-06/msg02204.php
Purpose - This will allow to catch syntax errors in pg_ident at the
Kohei KaiGai kai...@kaigai.gr.jp writes:
My preference is nothing are changed both pg_getmsgint64() of the backend
and routines under PQfn() of the libpq. Isn't it unavailable to deliver
int64-
value after the endian translation on the caller side?
Right. If we had to change anything on
2012/9/21 Tatsuo Ishii is...@postgresql.org:
Kohei KaiGai kai...@kaigai.gr.jp writes:
My preference is nothing are changed both pg_getmsgint64() of the backend
and routines under PQfn() of the libpq. Isn't it unavailable to deliver
int64-
value after the endian translation on the caller
On 09/20/2012 12:24:49 PM, Karl O. Pinc wrote:
I've had problems using pg_restore --data-only when
restoring individual schemas (which contain data which
has had bad things done to it). --clean does not work
well because of dependent objects in other schemas.
Before doing any more work I
On 21.09.2012 17:58, m...@rpzdesign.com wrote:
During the execution of ProcessUtility() function in
/src/backend/xxx/utility.c,
the CreateStmt node type is processed to create a table.
Is there a global function in the context of the backend process that
will deliver what the current database
Kohei KaiGai kai...@kaigai.gr.jp writes:
Tom, could you give us a suggestion which manner is better approach; whether
the PQfn should have responsibility for endian translation of 64bit-integer,
or
callers (lo_tell64 or lo_seek64)?
Adding anything inside pqFunctionCall is useless, unless we
On Sep 21, 2012, at 10:59 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I don't believe this has been thought through nearly carefully enough.
If CREATE SCHEMA created a schema and nothing more, then the proposed
implementation would probably be fine. But per spec, CREATE SCHEMA
can specify not
Dickson S. Guedes lis...@guedesoft.net writes:
I reviewed this v5 of patch:
- https://commitfest.postgresql.org/action/patch_view?id=907
The patch is small and implements a new syntax to CREATE SCHEMA
that allow the creation of a schema be skipped when IF NOT EXISTS is
used.
I don't
Heikki:
Thanks for the response. I am writing an external replication engine
and putting hooks into postgres to send signals via a unix socket to
the outside world.
All of the logic and implementation will occur OUTSIDE the postgres
codebase and
will not interfere with any WAL based
On Friday, September 21, 2012 08:12:26 PM m...@rpzdesign.com wrote:
Heikki:
Thanks for the response. I am writing an external replication engine
and putting hooks into postgres to send signals via a unix socket to
the outside world.
All of the logic and implementation will occur OUTSIDE
Andres:
Thanks for the link on the GIT patch code.
I did a big major domo search and found some stuff related to command
triggers:
http://archives.postgresql.org/pgsql-hackers/2012-03/msg00169.php
Look into the new event triggers started recently. -
Are these command triggers currently in
Hi,
On Friday, September 21, 2012 11:06:46 PM m...@rpzdesign.com wrote:
Thanks for the link on the GIT patch code.
I did a big major domo search and found some stuff related to command
triggers:
http://archives.postgresql.org/pgsql-hackers/2012-03/msg00169.php
Look into the new event
Tom, Kaigai,
Kohei KaiGai kai...@kaigai.gr.jp writes:
Tom, could you give us a suggestion which manner is better approach; whether
the PQfn should have responsibility for endian translation of 64bit-integer,
or
callers (lo_tell64 or lo_seek64)?
Adding anything inside pqFunctionCall is
On Sat, Sep 22, 2012 at 3:06 AM, David E. Wheeler da...@justatheory.comwrote:
On Sep 21, 2012, at 10:59 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I don't believe this has been thought through nearly carefully enough.
If CREATE SCHEMA created a schema and nothing more, then the proposed
(2012/09/21 22:32), Michael Paquier wrote:
On Fri, Sep 21, 2012 at 9:33 PM, Daniele Varrazzo
daniele.varra...@gmail.com mailto:daniele.varra...@gmail.com wrote:
On Fri, Sep 21, 2012 at 5:17 AM, Josh Kupershmidt
schmi...@gmail.com mailto:schmi...@gmail.com wrote:
I haven't
On Sat, Sep 22, 2012 at 9:08 AM, sakamoto dsakam...@lolloo.net wrote:
(2012/09/21 22:32), Michael Paquier wrote:
On Fri, Sep 21, 2012 at 9:33 PM, Daniele Varrazzo
daniele.varra...@gmail.com
mailto:daniele.varrazzo@**gmail.comdaniele.varra...@gmail.com
wrote:
On Fri, Sep 21, 2012 at
Tom, Kaigai,
Kohei KaiGai kai...@kaigai.gr.jp writes:
Tom, could you give us a suggestion which manner is better approach; whether
the PQfn should have responsibility for endian translation of
64bit-integer, or
callers (lo_tell64 or lo_seek64)?
Adding anything inside pqFunctionCall is
If the present project is having a tough time doing enhancements, I should
think it mighty questionable to try to draw it into core, that presses it
towards a group of already very busy developers.
On the other hand, if the present development efforts can be made more
public, by having them take
(2012/09/22 10:02), Christopher Browne wrote:
If the present project is having a tough time doing enhancements, I
should think it mighty questionable to try to draw it into core, that
presses it towards a group of already very busy developers.
On the other hand, if the present development
On Friday, September 21, 2012 8:28 PM Heikki Linnakangas wrote:
On 02.07.2012 15:08, Amit Kapila wrote:
Attached is a Patch to change the parsing of pg_ident.conf to make it
similar to pg_hba.conf.
This is based on Todo Item:
http://archives.postgresql.org/pgsql-hackers/2011-06/msg02204.php
On Fri, Sep 21, 2012 at 05:16:46PM +0800, Rural Hunter wrote:
I am thinking this query needs to be split apart into a UNION where the
second part handles TOAST tables and looks at the schema of the _owner_
of the TOAST table. Needs to be backpatched too.
OK, I am at a conference now so will
On Friday, September 21, 2012 6:50 PM Alvaro Herrera wrote:
Excerpts from Amit Kapila's message of vie sep 21 02:26:49 -0300 2012:
On Thursday, September 20, 2012 7:13 PM Alvaro Herrera wrote:
Well, there is a difficulty here which is that the number of processes
connected to databases must
2012/9/21 David E. Wheeler da...@justatheory.com
On Sep 21, 2012, at 10:59 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I don't believe this has been thought through nearly carefully enough.
If CREATE SCHEMA created a schema and nothing more, then the proposed
implementation would probably be
On Fri, Sep 21, 2012 at 3:14 PM, Milton Labanda 1000ton@gmail.com wrote:
Hi friends, wich context is the apropiate to install this plugin?
I have
Ubuntu 11
x64 architecture
postgresql 9,2
libv8-3.1 (system package)
but not get install it. Some ideas?
Well, I'm not sure if
45 matches
Mail list logo
