=# SELECT '[A]'::json,
array_to_json(ARRAY['A']),
array_to_json(ARRAY['A'::json]);
-[ RECORD 1 ]-+--
json | [A]
array_to_json | [A]
array_to_json | [\A\]
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
is deprecated interface - but it has necessary
functionality still - it support a writable statements.
So, dblink on FDW connection seems to be a possible solution.
We pass a query as a form of a plain text.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers
;
Parser error?
You need double-quotes around the name:
=# CREATE EXTENSION uuid-ossp;
CREATE EXTENSION
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
for now.
It would be reasonable if we had used automatic detection of
character encoding, but we don't. In addition, some crazy
encoding might use BOM codes as a valid character.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
also support COPY TO WITH BOM for writes.
Comments welcome.
--
Itagaki Takahiro
copy_from_bom.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
as documentation, we could
move them into internals section in the SGML doc tree. If so,
the translated README will be a part of the doc translation project.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
of 512.
Anyway, I'm not sure we need to include the query mode into the pgbench's
codes. Instead, how about providing a sample script as a separate sql
file? pgbench can execute any script files with -f option.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers
.
The similar problem exists in dblink_get_result and dblink_record_internal.
Attached patch fixes those problems.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
-META_COMMAND
instead of string comparison for each loop.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
() with/without timeout in the cases, no?
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
instead of the old pinned one.
Of course, copy-on-writing is more complex than skipping pinned pages,
but I wonder we cannot vacuum at all in some edge cases with the
skipping method.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
it wouldn't hurt too much.
Yes, probably. AFAIK, RHEL 5 cannot readahead in backward scans.
It might be improved in the latest kernel, but it would be safe
not to rely on kernels except simple forward scans.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
is preferred.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
- IDENTIFICATION $PostgreSQL$ in pg_collation.h, syncrep.h, and syncrep.c
Other files has their actual paths in the same place.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, Mar 10, 2011 at 12:55, Robert Haas robertmh...@gmail.com wrote:
On Wed, Mar 9, 2011 at 8:33 PM, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
I found trivial mistakes in the recently added files.
Will they fixed by some automated batches, or by manual?
I think these should
;
Is it reasonable? Or, do we have alternative ways for the same purpose?
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Feb 22, 2011 at 18:11, Cédric Villemain
cedric.villemain.deb...@gmail.com wrote:
2011/2/22 Itagaki Takahiro itagaki.takah...@gmail.com:
psql \d(+) doesn't show any information about UNLOGGED and TEMP attributes
for the table. So, we cannot know the table is unlogged or not unless
we
Here is a patch to support CREATE UNLOGGED TABLE in psql tab-completion.
It also fixes a bug that DROP is completed with TEMP and UNIQUE unexpectedly
and cleanup codes for DROP OWNED BY in drop_command_generator().
--
Itagaki Takahiro
psql_tab_completion_for_unlogged-20110223.patch
Description
to FDW developers'
opinions anyway. The text array is an example, but there should be many
other requirements. Personally, I'd like to have a method to list available
options from SQL. We should also consider column-level options for foreign
tables then.
--
Itagaki Takahiro
--
Sent via pgsql
; they are always created in pg_temp_N schema.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
16:04:50 UTC 2010
x86_64 x86_64 x86_64 GNU/Linux
* PG DB:
Name| Owner | Encoding | Collate | Ctype | Access
privileges
+--+--+-+---+---
contrib_regression | postgres | UTF8 | C | C |
--
Itagaki
On Fri, Feb 18, 2011 at 20:12, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
+ extern char *pg_any_to_server(const char *s, int len, int encoding);
+ extern char *pg_server_to_any(const char *s, int len, int encoding);
I applied the version with additional codes for file_fdw.
--
Itagaki
On Fri, Feb 18, 2011 at 03:57, Robert Haas robertmh...@gmail.com wrote:
On Wed, Feb 16, 2011 at 10:45 PM, Itagaki Takahiro
I am not qualified to fully review this patch because I'm not all that
familiar with the encoding stuff, but it looks reasonably sensible on
a quick read-through. I am
SEQUENCE us;
TRAP: FailedAssertion(!(relkind == 'r' || relkind == 't'), File:
heap.c, Line: 1246)
The most easiest fix would be preventing them in parser level.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
cache search doesn't seem like overhead.
We need to research what we should cache for conversion procs.
We will need 4 bytes per conversion pair if we cache only OIDs,
but sizeof(FmgrInfo) bytes if we use the same way as ToXXXConvProc cache.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing
On Thu, Feb 17, 2011 at 17:05, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
I did a few cosmetic fixes, mainly lmgr/README and make a subroutine
ReleaseLockForOwner() for LockReleaseSession and LockReleaseCurrentOwner.
Committed with a few typo fixes. Thanks, Marko!
--
Itagaki Takahiro
.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, but encoding names are not identifiers.
--
Itagaki Takahiro
copy_encoding-20110217.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. The extension
will lack of file encoding support, but still useful for many cases.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. I've applied the COPY API patch.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
sys/stat.h is needed.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
write_pipe_chunks(buf.data, buf.len, LOG_DESTINATION_CSVLOG);
pfree(buf.data);
+
+ return;
}
/*
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
of marking the patch Ready for
Committer.
Thank you very much for performance testing and reviewing!
The result is interesting because I didn't intend performance optimization.
At least no performance regression is enough for the purpose.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing
alternative solutions in the past discussion.
* csvlog_fields is marked as PGC_POSTMASTER. It can protect mixed formats
in a csv file on default log_filename, but other similar GUC variables
are usually marked AS PGC_SIGHUP.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list
. Then, please let me know functions you don't want to include
in the core, if any. I'll remove them at the same time.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
:
* Should we print foreign table names in error messages?
http://archives.postgresql.org/pgsql-hackers/2011-02/msg00427.php
* COPY encoding patch was rejected, but using client_encoding is
logically wrong for file_fdw. We might need subset of the patch
for file_fdw.
--
Itagaki Takahiro
function naming (sort_or_unique() ? really?),
Could you suggest better names?
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
: release all locks including session locks.
| allLocks == false: release all non-session locks.
* Or, we might have one subroutine for LockReleaseSession() and
LockReleaseCurrentOwner(). They have similar codes.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers
might be matters of preference.
I'd like to here about them form third person.
* name: log_csv_fields vs. csvlog_fields
* when to assign: PGC_POSTMASTER vs. PGC_SIGHUP
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
On Thu, Feb 10, 2011 at 19:37, Christoph Berg c...@df7cb.de wrote:
Currently, tab-completing :variable names in psql does not work at the
beginning of the line. Fix this by moving the code block before the
empty buffer case.
Seems reasonable to me.
--
Itagaki Takahiro
--
Sent via pgsql
didn't seem right. Anyone have an
idea where they should go or should I just add a new one?
I think you can add advisory_lock.sql for the test.
--
Itagaki Takahiro
advisory4fix.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Thu, Feb 10, 2011 at 09:30, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Trivial patch attached.
Applied. Thanks!
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
to complete
raw_fields support in CopyState. (Or, we should also revert changes
related to raw_fields.) However, we'd better postpone jagged csv
support to 9.2. The design is still under discussion.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
of infinity and return an error if that's the case? I
Maybe so. It also works if we had infinity on timestamp overflow, but
I've not tested yet. Anyway, we need similar fix for timestamp versions.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
On Wed, Feb 9, 2011 at 10:17, Andrew Dunstan and...@dunslane.net wrote:
Isn't this all really a bug fix that should be backpatched, rather than a
commitfest item?
Sure, but we don't have any bug trackers...
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers
to use pipe also on Windows.
* Research libpq + fork() issue. We have a warning in docs:
http://developer.postgresql.org/pgdocs/postgres/libpq-connect.html
| On Unix, forking a process with open libpq connections can lead to
unpredictable results
--
Itagaki Takahiro
--
Sent via pgsql-hackers
retrieve the
values. It's an existing issue, but will be more serious in 9.1.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
?topic=/com.ibm.db2.luw.sql.ref.doc/doc/r927.html
I'm not sure it is the best syntax, but at least it's easy to read
for beginners and works with parentheses completion by text editors.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
') AS a(x);
=# SELECT x FROM generate_series('infinity'::timestamptz, 'infinity',
'1 sec') AS a(x);
postgres=# SELECT x FROM generate_series(1, 9,-1) AS a(x);
postgres=# SELECT x FROM generate_series(1, 9,3) AS a(x);
They work as expected in 9.1dev.
--
Itagaki Takahiro
--
Sent via pgsql-hackers
-baserestrictcost.startup;
+ cpu_per_tuple = cpu_tuple_cost + baserel-baserestrictcost.per_tuple;
+ run_cost += cpu_per_tuple * 10 * baserel-tuples;
+ *total_cost = *startup_cost + run_cost;
+
+ return stat.st_size;
+}
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Sun, Feb 6, 2011 at 23:31, Stephen Frost sfr...@snowman.net wrote:
* Itagaki Takahiro (itagaki.takah...@gmail.com) wrote:
I think we need to improve postgresql.conf.sample a bit more, especially
the long line for #log_csv_fields = '...'. 330 characters in it!
#1. Leave the long line
field is shifted in your broken CSV file?
For example, the case you find AB,CD,EF for 2 columns tables.
I could provide a raw CSV reader for jagged files, but you still have to
cook the returned fields into a proper tuple...
--
Itagaki Takahiro
jagged_csv_api-20110204.patch
Description: Binary
types and fusion() for multiset types, but I prefer
overloaded fusion() to have both names.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. But I chose the same function name and syntax because
arrays *are* multisets by definition.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
PostgreSQL overloading, yes, arrays are multisets as far as
defining those standard compliant APIs is concerned. AFAIUI.
Yes, I'd like to use overloading.
Choosing arbitrary names increases learning costs for users.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers
to write functions with C for each kind of input files.
Note that pg_bulkload has a similar feature like as:
CREATE FUNCTION my_function(...) RETURNS record AS ...;
COPY tbl FROM 'file' WITH (make_record_from_line = my_function)
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql
, no?
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
should implement all the features in copy.c
rather than exported APIs.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Windows-specific codes from the first try.
I doubt Windows message queue is the best API in such console-based
application. I hope we could use the same implementation for all
platforms for inter-process/thread communication.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql
or remote_encoding.
* CopyState can have conv_proc entity as a member instead of the pointer.
* need_transcoding checks could be replaced with conv_proc IS NULL check.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
? -- if so, it would be nightmare...
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
objections, I will also commit it.
I don't have any objections for the patch, but we might also need
to add description about restartpoints into log_checkpoints option.
http://developer.postgresql.org/pgdocs/postgres/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT
--
Itagaki Takahiro
--
Sent
files.
Not sure what you're referring to here...? Can you elaborate? I'm not
great with the docs. :/
Could you try to make html in the doc directory?
Your new decumentation after
| These columns may be included in the CSV output:
will be unaligned plain text without some tags.
--
Itagaki
on the same resource at the same time, though we still need to show
exclusive and shared locks in different lines.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
(), and some of checkpoints during recovery
might don't want to sleep.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
Thanks. It's a reasonable reference.
But I reworded it as below, that we are using in other a few places.
The character sets supported by the PostgreSQL server are described in ...
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
to the current commitfest for reminder.
https://commitfest.postgresql.org/action/patch_view?id=528
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
)
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
that accept MULTISETs also accept ARRAYs.
For example, we will have cardinality(ARRAY) even if we have
cardinality(MULTISET). Also, trim_array() is in the SQL standard.
I can remove some parts in the patch, especially for parser changes,
but others should be still in the core.
--
Itagaki
is the consistent behavior for MD arrays. For example,
array_concat() is very strict, but @ and operators don't care about
the dimensions. I interpreted the second argument for trim_array() as
a number of elements, but of course we can redefine it as a number of
rows for MD arrays.
--
Itagaki
the easiest way if you use an external module.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
the extension is installed,
but it would be better to change the function to return just whole
extensions and JOIN with pg_extension in pg_available_extensions.
(it's the same technique used in pg_stat_replication)
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
to create in
BTW, I have a minor comments for the code.
extern bool extension_relocatable_p(Oid ext_oid);
What is _p ? Also, we could make the function static
because it is used only in extension.c.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
On Thu, Jan 27, 2011 at 22:48, Dimitri Fontaine dimi...@2ndquadrant.fr wrote:
Itagaki Takahiro itagaki.takah...@gmail.com writes:
I found pg_restore with -c option fails when an extension is created
in pg_catalog.
Nice catch, thank you very much (again) for finding those :)
Seems good
compared with FOREACH var IN expr.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
OR REPLACE
FUNCTION for others. We'd better write documentation about how to write
installer scripts because CREATE EXTENSION has some implicit assumptions
in them. For example, Don't use transaction, etc.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
or CREATE EXTENSION IF NOT EXISTS
rather than CREATE EXTENSION.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
want to optimize it, we could use memcpy() because slices are
placed in continuous memory. But I'm not sure the worth; I guess
FOREACH will be used with SLICE = 0 in many cases.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
file_fdw_validator HANDLER file_fdw_handler;
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
files.
* A declaration of assign_log_csv_fields() at the top of elog.c
needs extern.
* There is a duplicated declaration for build_default_csvlog_list().
* list_free() is NIL-safe. You don't have to check whether the list
is NIL before call the function.
--
Itagaki Takahiro
--
Sent via pgsql
, but will return a multiset when we
support true multiset data type.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
| |
(1 row)
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
the overhead, we should cache the conversion procedure
in CopyState. How about adding something like FmgrInfo file_to_server_covv
into it?
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
? Another solution might be adding a dummy assignment
after calls of die_horribly().
--
Itagaki Takahiro
noreturn.diff
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
think it is more robust way?
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, but I cannot see any
differences. But welcome if any of you could test on high-performance
servers.
Comparison with file_fdw would be more interesting
If they have similar performance, we could replace COPY FROM to
CREATE TABLE AS SELECT FROM foreign_table, that is more flexible.
--
Itagaki
with explainInfo
if we use XML or JSON for the format. For example, pgsql_fdw can
return the result from EXPLAIN (FORMAT json) without modification.
It might be one of the reasons we should should support JSON in the core :)
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers
for complex
FdwPlans. However, since we don't have any better solution for now,
we could have the variable for 9.1. It's much better than nothing.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
, we might not have to include JSON
in the core. We can download any JSON implementations from the
site after installing the core server. Of course, if we will
use JSON types in the core (EXPLAIN JSON output?), we have to
include one of them.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing
parameter. The best
place would be around the descriptions of loops in Using EXPLAIN page:
http://developer.postgresql.org/pgdocs/postgres/using-explain.html
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
,
but there is still the same issue -- we might have different
compressed results if we use different algorithm for TOASTing.
So, it would be better to apply the present patch as-is.
We can improve the comparison logic over the patch in another
development cycle if possible.
--
Itagaki Takahiro
--
Sent
logic for the security label table.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
?
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
results as
HeapTuple.
I think file_fdw can return tuples in virtual tuples forms,
and ForeignNext() calls ExecMaterializeSlot() to store tableoid.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
.
Is it possible or not?
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
pg_advisory_unlock_all();
pg_advisory_unlock_all
(1 row)
postgres=# ROLLBACK;
ROLLBACK
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
-to-one correspondence.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
), -- column position in csv file
t text[] OPTION (column 'all the rest'),
d dateOPTION (column 2)
) SERVER file_server
OPTIONS (format 'csv', filename '/path/to/ragged.csv');
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
as the hook.
file_fdw likes #1 because there are no external storage to store
statistics for CSV files, but pgsql_fdw might prefer #2 because
the remote server already has stats for the underlying table.
--
Itagaki Takahiro
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
be collect() aggregate function because
we might need to change the result type from array to multiset.
collect(anyelement) = anyarray for now
Note that fusion() won't be an issue because we can overload it:
fusion(anyarray) = anyarray and (anymultiset) = anymultiset
--
Itagaki Takahiro
1 - 100 of 888 matches
Mail list logo
