This is a kindly reminder, that this problem (message about "constraint"
violation, while there is no such a constraint defined, just an index) is
still unresolved.
Let's fix that naming?
Patch is attached in the previous message (posted to -bugs list)
On Thu, Mar 16, 2017 at 9
On Fri, Jul 29, 2016 at 5:28 PM, Jim Nasby wrote:
>
> The way I sum up MySQL vs PG for people that ask is to recount how they
> "fixed" the Feb. 31st bug when they released strict mode (something that
> they actually called out in the release PR). With strict mode enabled, Feb.
> 30th and 31st wou
On Fri, Jul 29, 2016 at 4:39 AM, Tatsuo Ishii wrote:
>
> Great translation.
>
> BTW, is there any opposite information, i.e. showing the limitation of
> MySQL comparing with PostgreSQL? I'm not familiar with MySQL, but
> occasionally hearing surprising (as a PostgreSQL user) limitation of
> MySQL
Following Uber's case discussion, I found this talk by Alexey Kopytov to be
really interesting:
http://kaamos.me/talks/pgday16/strongmysql/strongmysql.html (online html,
in Russian)
I translated it to English:
https://www.dropbox.com/s/t6a15s66jxg50tg/mysqlstrong_pgday16russia.pdf?dl=0
(pdf)
T
Hello hackers,
Consider a Postgres cluster containing several DBs (for example several
projects/sites). If one wants to optimize queries on one specified site --
what should he do? His obvious need is to switch full logging for the exact
database on, collect the logs and analyze them using pgFouin
Hello,
some app created tables ussing uppercase letters in table names (this app
was migrated from mysql). One tries to use \d to search tables info:
ru=# \d pnct_Board
Did not find any relation named "pnct_Board".
Of course, it works with ":
ru=# \d "pnct_Board"
Tab
On Thu, Jun 3, 2010 at 16:02, Andrew Dunstan wrote:
>
>
> Denis I. Polukarov wrote:
>
>> Hi!
>>
>> I'm to face a problem, and not at once resolve it.
>>
>>
> [default namespace mapped in xml "xmlns=" attribute requires corresponding
> mapping in third param of xpath()]
>
> It's a tolerably subtle
Hi,
I have a table "table1" with ~100k rows, the table having "flag1"
column. The value of "flag1" is NULL in 85k+ rows, and it's TRUE in
7k+ rows, and FALSE in 6k rows. I use EXPLAIN to get apprx. number of
rows for simple SELECT queries. But in case of "...WHERE NOT flag1"
the optimizer is compl
Hi,
I wonder, if the following is correct and provides expected result:
test=# select generate_series(1, 2), generate_series(1, 4);
generate_series | generate_series
-+-
1 | 1
2 | 2
1 |
On Nov 12, 2007 12:59 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> I'm not clear on what you're proposing. There is no such thing as an
> opclass with no operators (or at least, not a useful one), so this seems
> mutually contradictory.
>
> regards, tom lane
>
You're right, t
On Sep 25, 2007 10:57 AM, Pavel Stehule <[EMAIL PROTECTED]> wrote:
> Hello
>
> Current result from xpath function isn't indexable. It cannot be
> problem with possibility cast it to some base types.
>
> CREATE OR REPLACE FUNCTION xml_list_to_int(xml[])
> RETURNS int[] AS $$
> SELECT ARRAY(SELECT t
On 10/11/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> > On 10/11/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> >> Segfaults? That shouldn't happen. Please show a test case.
>
> > Test cas
On 10/11/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> > During restoration to 8.3 I've catched segfaults -- during INSERTs
> > into tables with "tsearch2"."tsvector" columns.
>
>
On 10/11/07, Florian G. Pflug <[EMAIL PROTECTED]> wrote:
>
> Maybe we could document some regexp, awk script, or similar that strips the
> tsearch stuff from such a table of contents?
Just my .02c for those who will work on migration manual.
In my case, all tsearch2 stuff was kept (before 8.3) in
Hubert recently posted his thoughts on this topic:
http://www.depesz.com/index.php/2007/09/16/my-thoughts-on-getting-random-row/
I've encountered with this problem several times in web development and
every time found out that the best (in terms of performance) solution is to
use some pseudo rando
The current (CVS version) configure script has the following options
(among many others):
--enable-dtrace build with DTrace support
--with-ossp-uuidbuild with OSSP UUID library for UUID generation
--with-libxml build with XML support
--with-libxslt build
On 9/28/07, Pavel Stehule <[EMAIL PROTECTED]> wrote:
> > We would create wrappers returning int[], bool[], string[], but there
> > are several issues with such functions:
> > - if the type of the data located on nodes that match XPath
> > expression differs from what is expected, what should we d
On 9/27/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> * Draft release notes --- can't really ship a beta without these,
> else beta testers won't know what to test. Traditionally this has
> taken a fair amount of time, but I wonder whether we couldn't use
> http://developer.postgresql.org/index.php/Wh
The problem with contrib/xml2's xpath_* functions (that return
scalars) was that they are very specific. If XPath expression
evaluation returns array of values (set of XML pieces), but the
function returns only the first, significant information is lost,
while there is no any gain in speed at all.
There is a problem with line feeds for contrib/xml2:
http://www.nan-tic.com/ftp/pgdoc/xml2.html
As for idea itself, I find it very useful (besides usability
improvements, it would help to promote Postgres advanced features).
On 8/29/07, Albert Cervera i Areny <[EMAIL PROTECTED]> wrote:
> I've bee
On 6/13/07, Gregory Stark <[EMAIL PROTECTED]> wrote:
I'm not a fan either so perhaps I'm biased, but this seems like a good example
of where it would be an *awful* idea.
Once you have an XML plan what can you do with it? All you can do is parse it
into constituent bits and display it.
"...and
On 6/2/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
On further consideration I don't see the necessity for this. We don't
say this about lib-ossp-uuid although it too is only used for a contrib
module.
And is it good? For that functionality I would also add comment
describing that this "--with
On 5/20/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
contrib is a misnomer at best. When 8.3 branches I intend to propose
that we abandon it altogether, in line with some previous discussions.
We can change the configure help text if people think it matters that
much - which seems to me much m
On 4/15/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Well, if we're going to make libxslt an explicit thing, then it'd be
trivial to add an xslt transformation function into the core, and then
I think we can claim equivalent support. But we'll have to check the
details, of course.
I have bee
On 4/10/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> I remember several cases when people (e.g. me :-) ) were spending some
> time trying to find an error in some pl/pgsql function and the reason
> lied in incorrect
On 4/9/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> As I can see here, when I ask for element that doesn't exist, the
> database returns NULL for me. Maybe it's well-known issue (and
> actually I unders
Thinking about XPath's output in cases such as 'SELECT xpath('/a', '');' I've realized that in such cases an empty array should be
returned (now we have NULL for such cases).
Why? Because database _knows_ that there is no element -- this is not
NULL's case ("unknown").
Then I've examined how the
On 4/5/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Nikolay Samokhvalov wrote:
[...]
> If I am wrong and it's better to leave libxml2-free capabilities, then
IMHO
> we need to reflect it explicitly in the docs, what requires libxml2, and
> what doesn't
Agreed, let'
On 3/23/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Andrew Dunstan wrote:
> Would it be better to use some more unlikely name for the dummy root
> element used to process fragments than ?
Why do we even need to support xpath on fragments?
Why not? I find it useful and convenient.
--
Be
On 3/27/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Where are we on this? Peter thought the consistency makes sense, but if
we can provide functionality that doesn't require libxml, why not
do it?
I'm still for --enable-xml and putting _everything_ XML-related under this
option. My main po
On 4/4/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Am Mittwoch, 4. April 2007 14:43 schrieb Nikolay Samokhvalov:
> > Why do we even need to support xpath on fragments?
>
> Why not? I find it useful and convenient.
Well, rather than inventing bogus root wrapper elements,
On 3/17/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
In principle I am in favor of the patch.
Would it be better to use some more unlikely name for the dummy root
element used to process fragments than ?
Perhaps even something in a special namespace?
I did think about it, but I didn't find
On 3/5/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
On 3/4/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
> I'll fix these issues and extend the patch with resgression tests and
> docs for xpath_array(). I'll resubmit it very soon.
Here is a new version o
What about it? W/o this not large patch XML functionality in 8.3 will be weak...
Will it be accepted?
On 3/5/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
On 3/4/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
> I'll fix these issues and extend the patch with r
On 3/6/07, Mike Rylander <[EMAIL PROTECTED]> wrote:
Attatched you'll find a patch that I've been kicking around for a
while that I'd like to propose for inclusion in 8.3. I attempted to
submit this through the original xml2 author (as far back as the 7.4
days) but got no response.
It's really
On 3/5/07, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
The XPath support is 1.0 or 2.0?
1.0
--
Best regards,
Nikolay
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On 3/5/07, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
From: "Nikolay Samokhvalov" <[EMAIL PROTECTED]>
> I've submitted patch for simple XPath 1.0 support (based on libxml2):
> http://archives.postgresql.org/pgsql-patches/2007-03/msg00088.php
But contrib/README.x
On 3/5/07, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
Is there any plan for supporting XQuery or XPath in 8.3?
I've submitted patch for simple XPath 1.0 support (based on libxml2):
http://archives.postgresql.org/pgsql-patches/2007-03/msg00088.php
This function does XML parsing at query time. So,
On 2/21/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
I think it would be better that leaving --with-libxml out (i.e.
compiling without libxml2 support) would only disable those parts in XML
functionality that require libxml2 for their implementation; the rest of
the stuff should be compiled in r
Now we have --with-libxml (and USE_LIBXML constant for #ifdef-s), what
is not absolutely right: XML support is smth that is more general than
"using libxml2 library". E.g., some SQL/XML publishing functions (such
as XMLPI) do not deal with libxml2.
Also, in the future more "non-libxml" functional
On 2/7/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
Nikolay Samokhvalov wrote:
>
> I still do not understand why is it so needed.
> Your argument is "some apps aren't able to call functions as
> schemaname.functionname(arg1, arg2, ..)", right?
wrong.
>
>
On 2/7/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
I still think that separate namespaces for extensions is a good idea
while adjusting search_path is not. I've explained my POV in details
several messages ago in this thread...
Separation of extensions with fully spec
On 2/6/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
If the extension installs everything in dedicated namespace(s), I think
we would want to have an option to add those namespaces easily to search
paths. Right now all we can do is to set a search path. It would be
nice, for example, to have supp
On 2/5/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
[...]
I would suggest we start with what is (I think) simplest and clearest:
. catalog support via a simple extension->schema(s) map
. initdb installs standard extensions if it finds them, unless told not to
. support for adjusting search path
On 1/30/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
[...]
4. visibility/searchpath issues. I don't think long search paths are a
huge issue, but I think we can make life a bit easier by tweaking
searchpath support a bit (David's clever SQL notwithstanding).
As for search_path -- is it reall
BTW,
Moreover, I would like xpath_string() which return
On 1/29/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
[...]
So, while I realize that I've been arguing for a lean core recently, I
want to propose that we add a small set of XPath support functions to
the core. This would come down to
On 1/25/07, Teodor Sigaev <[EMAIL PROTECTED]> wrote:
It's should clear enough for now - dump data from old db and load into new one.
But dump should be without any contrib/tsearch2 related functions.
Upgrading from 8.1.x to 8.2.x was not tivial because of very trivial
change in API (actually no
Discussion "tsearch in core patch, for inclusion" shows
(http://archives.postgresql.org/pgsql-hackers/2007-01/msg01165.php and
following http://archives.postgresql.org/pgsql-hackers/2007-01/msg01186.php)
that there are some problems with contrib promotion and expansion.
I've encountered with bad
On 1/15/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Client encoding is A, server encoding is B. Client sends an xml datum
that looks like this:
INSERT INTO table VALUES (xmlparse(document '...'));
Assuming that A, B, and C are all distinct, this could fail at a number
of places.
I sugges
On 1/11/07, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
Duplicate versions of functions (e.g., there would be XMLPATH() as the
main XPath function for XML type, producing arrays of values of XML type in
general case -- non-standard, but generalized).
Sorry :-) I wanted to say I s
Duplicate versions of functions (e.g., there would be XMLPATH() as the main
XPath function for XML type, producing arrays of values of XML type in
general case -- non-standard, but generalized).
In addition to two SQL files for registration of module functions in
database, I would move XSLT funct
ake <[EMAIL PROTECTED]> wrote:
On Sun, 2006-12-24 at 20:45 +0300, Nikolay Samokhvalov wrote:
> So, can anybody help me?..
Moving to pgsql-www:
Just create an account:
http://developer.postgresql.org/index.php?title=Special:Userlogin&returnto=XML_Todo
>
> On 12/24/06, Nikolay Sa
So, can anybody help me?..
On 12/24/06, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
Surely, I've created one (nickname: Nikolay) and are trying to do
things being logged in :-)
On 12/24/06, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> Nikolay Samokhvalov wrote:
> >
On 12/24/06, Tom Lane <[EMAIL PROTECTED]> wrote:
What I'm wondering about is why this printout is emitted as a separate
DEBUG message ... wouldn't it be better to incorporate it as the DETAIL
field of the error message?
Surely, it would. But the thing is that I couldn't manage to format
libxml2
Surely, I've created one (nickname: Nikolay) and are trying to do
things being logged in :-)
On 12/24/06, Magnus Hagander <[EMAIL PROTECTED]> wrote:
Nikolay Samokhvalov wrote:
> I want to collect all XML todo issues (from my list, from Peter's and
> those Tom just describe
I want to collect all XML todo issues (from my list, from Peter's and
those Tom just described in "Loose ends in PG XML patch") in one
place, to make the overall picture clear for everyone.
How can I gain access to developers wiki? (Actually, I've created the
page"XML Todo" - http://developer.post
Another thing that was removed is XMLCOMMENT..
On 12/22/06, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
Hmm... In my patch (http://chernowiki.ru/index.php?node=98) I didn't
remove this, moreover I've fixed a couple of issues...
Looks like it was removed by Peter (both patche
Hmm... In my patch (http://chernowiki.ru/index.php?node=98) I didn't
remove this, moreover I've fixed a couple of issues...
Looks like it was removed by Peter (both patches he mailed lack it).
Actually, without this function a set is SQL/XML publishing functions
becomes rather poor.
Peter?
On
another way is:
export CPPFLAGS=$(xml2-config --cflags); ./configure --with-libxml
I think that such thing can be used in configure script itself,
overwise a lot of people will try, fail and do not use SQL/XML at all.
On 12/22/06, Pavel Stehule <[EMAIL PROTECTED]> wrote:
Hello,
I try to compil
On 11/17/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Alvaro Herrera wrote:
> We should also take the opportunity to discuss new keywords for the
> XML support -- will we use new grammar, or functions?
The XML stuff is defined in the SQL standard and there are existing
implementations, so any
On 10/9/06, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
Maybe my understanding is wrong - I'll be glad to hear why.
Maybe at least to create special switcher for database settings? (It
would remain backward compatibility...)
--
Best regards,
Nikolay
---
On 10/9/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Duplication of code and functionality with pg_dumpall.
Well, then "-C" option of pg_dump can be considered as duplication of
pg_dumpall's functionality too, right?
I'd want to see
some thought about how to resolve that, not just a quick copy-som
What is the reason to not include database settings (like search_path)
to database dump created with "pg_dump -C"?
For me, I've created tmp patch for pg_dump to make my system work
(patch for CVS version is included).
-- Forwarded message ------
From: Nikolay Samo
On 8/26/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Bruce Momjian wrote:
> I made it clear in the section that the XML syntax was being checked,
> not validation against a schema. You want Check and Validation
> sections?
"Valid" and "well-formed" have very specific distinct meanings in XML
On 8/26/06, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
[...]
If you decide to include the mentioning about contrib/xml2 to docs, I
would suggest the patch for this module. The patch renames that
function to xml_check() and adds xml_array() (issue from the current
TODO). Or it's t
On 8/26/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Bruce Momjian wrote:
> Validation
> --
> /contrib/xml2 has a function called xml_valid() that can be used in
> a CHECK constraint to enforce that a field contains valid XML. It
> does not support validation against a specific XML sc
Is there any way to control (enable/disable) some parts of BKI file?
(actually, I mean not BKI files themselves but their prototypes -
include/catalog/pg_*.h)
For example, I add some function to include/catalog/pg_proc.h and want
to have ability to enable/disable it during installation process
(e
Hello,
Recently an interview with Marten Mickos (mysql's ceo) appeared in
russian IT news (eg http://citcity.ru/12776/). I'd like ask some
[similar] questions to PostgreSQL core developers and write an article
in Russian. Actually, I'm sure that there is a great lack of PG news
in our mass media.
Actually, project mentioned on Oleg's page is only in plan.
I see some gap between current moment and the moment when GiST will
come to power for XML support - check out my proposal
(http://archives.postgresql.org/pgsql-hackers/2006-05/msg00044.php),
the 'minumum' list is that gap. When we will h
Yes, there is no single way, because there are different tasks. There
are many papers on this theme.
I'm pretty sure that first of all we need to analyze other DBMSes'
experience. I'm working on it, analyzing MS, ORA and DB2 (first
results of analysis will be available in several weeks).
I've su
Proposal: XMLType for PostgreSQL.
*** Minimum: ***
to have special type support for storing XML data and working with it.
This means following:
- ability to define any column of a table as of XMLType; internally,
all data is stored as VARCHAR;
- auto validation of documents against XML schema, if
71 matches
Mail list logo