Richard Broersma Jr wrote:
It seems the OP's connection string was set to localhost. Would this still
indicate a Name Loopup problem?
Do you have some some firewall running ? Also is there a localhost entry
in your hosts file(e.g /etc/hosts or C:/windows/system32/drivers/etc) ?
s stuff is killing me... func B is small, all table lookups optimized to
the hilt but still I'm taking major performance hit as it's called
hundreds/thousands of times.
Any ideas?
Thx,
Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to you
ding a new message as well. This Q is
probably better asked in respective JMS server group I guess.
Peter
I'm
running Ubuntu Karmic, installed from stock PG repositories. Whats going on
here?
Peter
sting... me is being forced to use stooped Outlook...
Peter
>After upgrade to 8.4.1 Perl "my" variables are no longer being seen by
subroutines:
>
> CREATE OR REPLACE FUNCTION global.perl_test()
> RETURNS "varchar" AS
>$BODY$
>my $test="
Why don't you try to
use another account for the service - while reinstalling just fill in 'posgres2'
as service account...
Best regards,
Peter
- Original Message -
From:
usya usya
To: pgsql-general@postgresql.org
Sent: Friday, March 04
and insert into ...
select union is by far more efficient than multitude of inserts.
Postgres 8.1.3, FreeBSD.
Has this (maybe) been fixed in most recent release?
Peter
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Martijn van Oosterhout wrote:
On Wed, Sep 27, 2006 at 12:14:44PM +0300, Peter wrote:
create table temp(a timestamptz);
insert into temp(a) select NULL; /* this passes */
insert into temp(a) select NULL union select NULL; /* fails:
ERROR: column "a" is of type timestamp
Multiple comma-separated values lists will also work... but I dont
think I have time to wait for 8.2...
thanks for all the tips!
Peter
utput data.
Any suggestions?
TIA,
Peter
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
;s
timestamptz. Rather messy.
I tried defining my own base type using timestamptz _in and _out
functions, and it seems to work. Had to re-create half of my database
objects due to dependencies, but now that it's done it seems to work
quite well.
Peter
id_1, but different id_2 and have
difference in time less than 5 minutes.
In this case this is record 1 and record 3.
How can I do this ?
Thanks in advance for your help.
Peter
---(end of broadcast)---
TIP 5: don't forg
and user_id=get_effective_user() and is_visible
Owner user (the one who owns the proc) always gets expected behaviour
from the proc (single quote instead of two single quotes). Other users
(all or nearly all) get two single-quotes on some strings (always the
same strings).
We're running Postgres 8.1.3 FWIW
Any ideas?
Peter
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
tion:=coalesce(conf_field_capt[i],'');
retval.field_index:=0;
retval.field_value:='';
retval.field_listsource:=sListSource;
retval.field_type:=coalesce(conf_field_type[i],'');
retval.field_attr:=sFieldAttr;
end if;
return next retval;
end loop;
Peter
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
:varchar as
field_name...'
There's a quote_ident() function too - details in the "string
functions" section of the manuals.
Allright, the quote_literal() function helped to a certain extent. One
field is now always properly formatted, and one other sometimes is
quoted... an
lve calls to user-defined
funcs.
We upgraded to 8.1.4 overnight, and I rewrote my code to use
quote_literal() function, and that seems to have helped - at least
results are now consistent across users. I still have no idea what was
the cause, but it was definitely there
Peter
iable number of
parameters), also I personally hate 'select * from my_func() as table(x
varchar)' syntax... system should be able to omit the table structure
definition and pick it up from function return.
Oh well, back to work.
Where do we submit wishlist entries, anyway?
Peter
-
t in 600 ms.
Why SELECT takes 3+ second to execute? Is it something to do with my
Postgres server optimization, or PgAdmin does not show correct data
retrieval runtime (leaks over into query runtime or something)?
This is PG 8.1 on FreeBSD, server is fairly powerful PC.
Peter
--
usually.
Try SELECT count(*) FROM ... instead and see if the times are closer.
Correct. That executes in 300ms flat:
Total query runtime: 301 ms.
Data retrieval runtime: 380 ms.
1 rows retrieved.
Peter
---(end of broadcast)---
TIP 4: Have you searched
first
case, but with 'SELECT INTO' almost no data are sent over the connection
(it all happens in the server).
I assumed the same thing. However, 'data retrieval runtime' as reported
by PgAdmin is really small compared to 'query runtime'... I would expect
it to be other way around
Thanks!
Peter
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
ead
How old a pgAdmin are you using?
1.4.3
I tried 1.5 but it was too slow rendering results from SELECT queries...
maybe it's fixed by now
Peter
---(end of broadcast)---
TIP 6: explain analyze is your friend
et in the warehouse, the sum of articles is updated in articles database.
Why are you trying rules? Trigger function would be much more logical
choice. There are some limitations in RULE syntax that won't let you use
all SQL statements there, so trigger might be your only way o
periodically, but that involves delay and added point
of failure (if cron process stops working for whatever reason). Ideally
async trigger proc would be the solution, but it seems I cant do
asynchronous execution in PG.
Thanks!
Peter
---(end of broadcast
he
domain 'email' to the new datatype. I can not figure how to do it with
"alter domain" syntax.
Thanks in advance for your help :-)
Kind regards,
Peter
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner wil
Hi,
Thanks for the suggestion. However I just wanted to give a brief
description of something I want to achieve. I believe such feature will
be very useful in more complicated environments.
Kind regards,
Peter
Michael Glaesemann wrote:
On Feb 19, 2006, at 2:12 , Stephan Szabo wrote
w only way to make this work is to build
SQL script with hundreds of calls to the stored proc in question, and run it
directly.
Any ideas?
Peter
cascaded updates and stuff. Care to see full text of the proc?
It's pl/PgPerlU
Peter
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
thou. Obviously performance would be better in this case as query
plans will be pre-compiled.
Peter
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On 3/14/15 3:27 PM, Миша Тюрин wrote:
> should we add disclaimer in pitr documentation about cp and fsync?
>
> cp does not fsync.
>
> and dd for example can do fsync.
only on some platforms
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
indexes.
[1]
http://pgeoghegan.blogspot.com/2015/01/abbreviated-keys-exploiting-locality-to.html
--
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
upstream txid of the transaction which actually made the change
originally (which only makes sense on that node) - but on the local node
receiving the change via BDR LLSR.
Can that be done?
/Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to you
On 2015-03-25 12:32, Craig Ringer wrote:
On 25 March 2015 at 19:15, Peter Mogensen wrote:
Say ... I have a table in a BDR replicated database with an "ON UPDATE"
trigger. - and that trigger wants to locally find out the local
txid_snapshot_xmin() when a change was applied to the
d.
Yes, that would serialize the selects...
It's very complicated to integrate into the cache however, since it
doesn't really know about how the values to cache are retrieved.
/Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
e node - and that's a
fast track to data divergence that can cause replication stalls and so on.
For the use case at hand, that's not a problem. The trigger would only
need to update a fully local state. - like a table not part of the
replication set and not related to any other tables.
ct in observing that the xmin column gives me the a local
txid of the transaction inserting the invalidation event - even if it
was originally inserted on another node, then I think it'll work.
/Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
On 4/20/15 6:09 PM, Bruce Momjian wrote:
> On Mon, Apr 20, 2015 at 07:06:37PM -0300, Alvaro Herrera wrote:
>> ISTM there's a documentation bug here: in the code, the "dump" method
>> checks for tablespaces and raises an error if they are found, but the
>> "upgrade" method does not check. I think t
d all txids will be larger than any xmin. And
I can't get the epoch of the xmin value.
BUT ... will this work: ?
Comparing
txid_current() of the SELECT transaction,
to
txid-current()-age(xmin) of the table row?
/Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.or
On 5/9/15 10:47 AM, Bill Moran wrote:
> https://wiki.postgresql.org/wiki/RPM_Packaging
>
> The link to the specfiles and other data at
> http://svn.pgrpms.org/repo/ gives a 404.
It's been move to git. I have updated the wiki page with the new URL.
--
Sent via pgsql-general mailing list (pgsq
On 2015-05-12 06:06, Craig Ringer wrote:
On 11 May 2015 at 21:10, Peter Mogensen wrote:
So ... I can easily get the current txid of the SELECT transaction by
calling txid_current().
Note that by doing so, you force txid allocation for a read-only query that
might otherwise not need one
On 2015-05-12 06:06, Craig Ringer wrote:
On 11 May 2015 at 21:10, Peter Mogensen wrote:
So ... I can easily get the current txid of the SELECT transaction by
calling txid_current().
Note that by doing so, you force txid allocation for a read-only query that
might otherwise not need one
onsistency / trouble. Would
anyone have thoughts on best practices for handling?
Thank you!
Peter
On 5/21/15 12:12 PM, Andomar wrote:
> Hi,
>
> Today I installed pgbouncer. I added a second installation as a hot
> standby. Before starting the standby, I configured "recovery.conf" to
> connect to pgbouncer.
>
> This results in an error message:
>
> Pooler Error: Unsupported startup para
gards,
Peter
On Thu, May 21, 2015 at 8:06 PM, Ian Barwick wrote:
> On 21/05/15 04:23, Peter Swartz wrote:
> > I'm creating a foreign table (foo_table) in database_a. foo_table lives
> in
> > database_b.foo_table has an enum (bar_type) as one of its columns.
> Because
>
Thank you for the message Tom; sounds great. I'll try that out, will check
on the planner's resultant behavior and email back.
Peter
On Sat, May 23, 2015 at 12:35 PM, Tom Lane wrote:
> Peter Swartz writes:
> > suppose the foreign database adds a value to the enum, and th
On 5/18/15 10:52 AM, Filipe Pina wrote:
> But one of the functions I need to create needs to accept an array of
> records.
PL/Python doesn't support that. Some more code needs to be written to
support that. You did everything correctly. I don't know of a good
workaround.
--
Sent via pgsql-g
On 5/28/15 5:35 PM, Randall Lucas wrote:
> Can I compile my own version of uuid_out and update the system
> catalogs, or create a "uuid_dashless" type that uses my own custom
> uuid_dashless.c that's hacked to remove dashes?
Either one would work.
--
Sent via pgsql-general mailing list (pgsql-
: 0 errors from 0 contexts (suppressed: 0 from 0)
There is still reachable data. Is this a bug or have I forgotten to free
something?
Best,
Peter
ation isn't acceptable. ON CONFLICT DO UPDATE
should be preferred once 9.5 is released.
[1]
http://www.postgresql.org/docs/9.4/static/plpgsql-control-structures.html#PLPGSQL-UPSERT-EXAMPLE
--
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgres
Hi,
I've got a function with 5 dblink select statement all to my local server
with the same connection string.
When one more dblink select statement is added the query fails.
Is there some kind of limit that I can configure? If so, which one an where?
Thanks,
Peter
A restart of my system solved the matter.
2015-07-05 20:54 GMT+02:00 Peter Kroon :
> Hi,
>
> I've got a function with 5 dblink select statement all to my local server
> with the same connection string.
> When one more dblink select statement is added the query fails.
>
Hi,
Every now and then my program will abort.
IAnd this is because: conn = PQconnectdb(conninfo);
The error given:
*** Error in `./server_prog': malloc(): smallbin double linked list
corrupted: 0x092c10a0 ***
Any thoughts on why I'm getting this message?
Regards,
Peter
RDS
"PostgreSQL 9.4.4 on x86_64-unknown-linux-gnu, compiled by gcc (Debian
4.7.2-5) 4.7.2, 64-bit"
The attachment is the program I've used for testing.
2015-07-18 0:15 GMT+02:00 Tom Lane :
> Peter Kroon writes:
> > Every now and then my program will abort.
> > IAnd
On 7/30/15 6:13 AM, Renato Oliveira wrote:
> We have a Nagios plugin, which monitors pg_locks and almost daily we see
> 3000 to 4 pg_locks.
>
> Can we just ignore them, can we let them grow without worrying?
>
> How many pg_locks are considered unsafe for any given postgres server?
That depe
nstall of the db and libpq.
Best,
Peter
2015-07-31 12:05 GMT+02:00 Albe Laurenz :
> Peter Kroon wrote:
> > I've found perhaps a bug.
> > I've narrowed down my code and the problem is indeed at: conn =
> PQconnectdb(conninfo);
> >
> > My connection string:
ordering by anyway, so you can
just not concatenate the ', ' string (so name_last || name_first), and
it will work as you expect, I believe.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
, based on what you say here, I
think you should actually "ORDER BY name_last, name_first".
--
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 9/15/15 1:48 AM, Ben Chobot wrote:
> We're in a situation where we would like to take advantage of the pgpass
> hostname field to determine which password gets used. For example:
>
> psql -h prod-server -d foo # should use the prod password
> psql -h beta-server -d foo # should use the beta pa
I think it would be really handy if temp_tablespaces were made resilient
against everything going away in the event of a hard crash.
--
Regards,
Peter Geoghegan
was superseded by a new version.
[1]
http://www.postgresql.org/message-id/CAEYLb_UTMgM2V_pP7qnuKZYmTYXoym-zNYVbwoU79=tup8h...@mail.gmail.com
--
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
as carrying on, because there
is no reason to think that the locale thing can easily be rolled back.
That was my point, in fact.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/
rst
version that happens to have ICU support). I don't like suggesting a
solution that I myself am unlikely to find the time to work on, but in
the long run that's the only sensible approach IMV.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@post
so that the collations simply never
go away, but if that does happen (or if you decide that the changes to
a collation matter for cultural or correctness reasons) then you can
at least detect the change and recover from it reliably.
ICU has some other really nice features, too, but that's ano
r are their collations graven on stone tablets, unlike
> anyone else's?
See my response to Thomas.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ing together using COMMENT ON
FUNCTION [...]:
https://www.postgresql.org/docs/current/static/sql-comment.html
Kind regards
Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
s no unique or exclusion constraint matching the ON CONFLICT
> specification
>
> If anyone knows what I'm doing wrong and how to get this to work, or knows
> that this is not possible to achieve, I'm all ears.
That should work. Are you sure you haven't spelled it "...
Hi,
I have the following setup:
Database Local has a table L1
Database Remote has a table R1 and a table R2.
Table Remote.R1 has a trigger. This trigger updates Remote.R2
I create a foreign table F1 on Database local which points to Remote.R1
When updating F1 the trigger on Remote.R1
ase replication and backup processes.
This belongs on the pgsql-jobs mailing list, not pgsql-general.
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
anywhere anymore, you can check out
the tag REL9_4_BETA1 from git and built it yourself.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
in the same
session. Obviously there would be way to minimize that risk but
things would start to get messy.
Any ideas would be much appreciated.
Kind regards
Peter Devoy
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
@David, thanks for the tip.
>Providing a concrete example might help.
My use case is a database with a large number of spatial tables. I
have written a spatial search function which, given an arbitrary table
extended with PostGIS, will search for records in that table whose
geometries are within
>Outputs two columns, one polymorphic match and one constant.
Nice.
>I couldn't figure out a way to get the output into columns.
I have had a fair play and am struggling also. Seems like any work around
is going to be too unholy to be worth running.
Thanks for having a crack!
Peter
re
complicated than it first appears, if you expect UPSERT to worry about
lock starvation, "unprincipled deadlocks" [1], and other problems like
that.
[1]
https://wiki.postgresql.org/wiki/Value_locking#.22Unprincipled_Deadlocking.22_and_value_locking
--
Peter Geoghegan
--
Se
e that made that untrue in
1981, if only barely [1], but the lesson for me was to take his claims
in this area with a generous pinch of salt.
[1] https://www.cs.cmu.edu/~pavlo/static/papers/stonebraker-ic2e2014.pdf
(See his citation 11)
--
Peter Geoghegan
--
Sent via pgsql-general maili
is far weaker. What specifically do you say is wrong about his
> current claims, and on what facts to you base it?
I'm not the one making overarching conclusions. I'm not trying to
convince you of anything.
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@
here is a similar consideration for DO UPDATE. I'm
slightly surprised that you're contemplating just ripping the check
out. Did I miss something?
[1] https://www.postgresql.org/message-id/57ee93c8.8080...@postgrespro.ru
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgs
Vitaly have said, there is
> literally no concurrent update.
I think that you have the right idea, but we still need to fix that
buffer lock bug I mentioned...
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to you
On Wed, Oct 12, 2016 at 1:41 PM, Kevin Grittner wrote:
> Aren't these two completely separate and independent bugs?
Technically they are, but they are both isolated to the same small
function. Surely it's better to fix them both at once?
--
Peter Geoghegan
--
Sent via pgsql-ge
T DO NOTHING code to avoid false positives where we can.
Do you intend to propose a patch to do that?
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ult.
I was under the impression that false positives of this kind are
allowed by SSI. Why focus on this false positive scenario in
particular?
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.o
27;m still not even clear on
whether you are actually arguing that they are special. (Except, of
course, the multi-value case -- that's clearly not okay.)
So, with the fix proposed by Thomas applied, will there be any
remaining false positives that are qualitatively different to existing
false p
erspective.
What are your thoughts on the back-and-forth between myself and Tom
concerning predicate locks within heap_fetch_tuple() path last
weekend? I now think that there might be an outstanding concern about
ON CONFLICT DO NOTHING + SSI here.
--
Peter Geoghegan
--
Sent via pgsql-
rmine
that it would be just fine to use the C locale, since the user isn't
entitled to assume anything about the exact sort order. There are of
course cases where this can make a huge difference.
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
ardinality leading attribute, so
this habit works against tuplesort. (Assuming a leading attribute of
pass-by-value type, or with abbreviated key support.)
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
search?utf8=%E2%9C%93&q=PDO
KR
Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
The comments in here may be of help:
https://github.com/postgres/postgres/blob/master/src/include/mb/pg_wchar.h
Kind regards
Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
_type;
>
> I wonder what the benefit of a typed table is and when this would be useful?
One use is with PL/Proxy. You create the type on the proxy, thus
allowing you to define functions using the type. Then create the table
on the backend from the type, thus ensuring they are
Hi All,
I'm relatively new to postgres after inheriting this server from a
previous admin so please bear with me if these are obvious questions.
My scenario:
* Last weekend I had a scheduled maintenance window for power/air
conditioning work.
* Prior to this outage the server was running
On 14/12/2015 11:39 AM, John R Pierce wrote:
> On 12/13/2015 4:22 PM, Peter Brady wrote:
>> Again there appears to be nothing logged to indicate why the server
>> is not starting at this point.
>
> the standard versions of postgres for RHEL/CentOS leave two sets of
> logs
get anything to work so any
help would be very much appreciated.
Thanks for reading
Peter Devoy
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
>Argh! I *always* type the wrong one. It should be %I instead of %L
You're not alone, I did the same thing in my example with quote_literal. -_-
Thank you all very much for your solutions -- I can end this 14hr day
on a high note!
Peter
--
Sent via pgsql-general mailing list (pgsql
> Hope this may be useful
Thanks for sharing!
Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
to Postgres:
https://www.youtube.com/watch?v=UgcC_bY4rPg
If I recall correctly JSON functionality was touched upon but, if you
have not seen it, the whole talk is worth a watch.
Hope this helps in some way.
Kind regards
Peter Devoy
--
Sent via pgsql-general mailing list (pgsql-general@postgr
g') ON CONFLICT (name) DO UPDATE SET
name='dog' RETURNING animal_id;
Is there a reason DO NOTHING was not developed for use with RETURNING?
Either way, upsert is great, I am glad we have it now.
Kind regards
Peter Devoy
On Mon, Mar 14, 2016 at 12:28 PM, Peter Devoy wrote:
> Is there a reason DO NOTHING was not developed for use with RETURNING?
I don't know what you mean. It should work fine with RETURNING.
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
er way. Maybe ON CONFLICT DO SELECT where the select
> operates over the target row.
Seems reasonable.
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
did;
http://www.postgresql.org/docs/9.3/static/sql-insert.html
Kind regards
Peter
On 14 April 2016 at 14:50, Ritanjali M wrote:
> Hi Team,
>
> I am new to postgresql ,i need to create one function where i have to insert
> data into cross database table from that table identity va
> Although people commonly use $foo $bar in examples, it is actually a misuse
> of a VERY rude acronym.
> The next time you need to make an example, please try being a little more
> original (or meaningful) with your variable names.
In light of recent CoC decisions, I would like to propose the
it's the answer but maybe another thing to look at...
All the best
Peter
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
scheme-like syntax, and the storage model would be properly relational (eg no
> duplicate rows).
Have you heard of QUEL?
See https://en.wikipedia.org/wiki/QUEL_query_languages
--
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your sub
Hi Peter!
The solution to this problem would be also interesting for me. We have
application which use sending data to background worker and it's look like
the asynchronous notification can be ideal solution. But we do not found
solution how to work with this notifications. Worker calcul
1 - 100 of 2098 matches
Mail list logo
